Autonomous ground vehicles deployed from facilities

ABSTRACT

Autonomous ground vehicles (“AGVs”) may be deployed from facilities (e.g., materials handling facilities, etc.) to deliver items to specified locations (e.g., user residences). In various implementations, AGVs may utilize various techniques for long-range travel between materials handling facilities and delivery locations (e.g., solar charging, strategically placed charging stations, energy efficient travel paths, etc.). In various implementations, AGV facilities (e.g., smaller types of materials handling facilities) may be sized to be more easily located in compressed urban areas (e.g., to be closer to various delivery locations, etc.) and may function as home base locations where AGVs are stationed and/or where items are received (e.g., from transportation vehicles) for delivery to local delivery locations.

BACKGROUND

Many companies, including “big box” retail and mail-order companies,package items (e.g., books, CDs, apparel, food, etc.) and/or groups ofitems together to be shipped in fulfillment of requests from customers(e.g., internal or external, retail or wholesale customers). Retailers,wholesalers, and other product distributors (which may collectively bereferred to as distributors) typically maintain an inventory of variousitems that may be ordered by customers. This inventory may be maintainedand processed at a materials handling facility. Such materials handlingfacilities may include, but are not limited to, one or more of:warehouses, distribution centers, cross-docking facilities, orderfulfillment facilities, packaging facilities, shipping facilities, orother facilities or combinations of facilities for performing one ormore functions of material (inventory) handling.

Ordered items are typically packed in shipping packages (e.g.,corrugated boxes) and shipped to the customer's residence or place ofbusiness. The delivery of physical items to a customer's specifiedlocation is traditionally accomplished using a delivery system includinga human controlled truck, bicycle, cart, etc. For example, a customermay order an item for delivery to their home. The item may be picked bya human agent from a materials handling facility, packed and shipped tothe customer for final delivery by a shipping carrier, such as theUnited States Postal Service, FedEx, or UPS. An agent of the shippingcarrier will load the item onto a truck that is driven to the finaldelivery location and a driver, or another human companion with thedriver, will retrieve the item from the truck and complete the deliveryto the destination. Over time, an increasing frequency and volume ofdeliveries of items from e-commerce and mail-order companies hasresulted in an increased need for faster and more efficient deliverymethods.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical components or features.

FIG. 1 illustrates a broad view of the operation of a materials handlingfacility, according to some implementations.

FIG. 2A depicts a block diagram of a side view of an autonomous groundvehicle, according to an implementation.

FIG. 2B depicts a block diagram of a side view of another autonomousground vehicle, according to an implementation.

FIG. 2C depicts a block diagram of a side view of another autonomousground vehicle, according to an implementation.

FIG. 3 depicts a block diagram of an autonomous ground vehicleenvironment, according to some implementations.

FIG. 4 depicts a block diagram of another autonomous ground vehicleenvironment, according to some implementations.

FIG. 5 depicts a block diagram of another autonomous ground vehicleenvironment, according to some implementations.

FIG. 6 depicts a block diagram of another autonomous ground vehicleenvironment, according to some implementations.

FIGS. 7A-7C depict block diagrams of another autonomous ground vehicleenvironment, according to some implementations.

FIG. 8 depicts a block diagram of another autonomous ground vehicleenvironment, according to some implementations.

FIG. 9 is a flow diagram illustrating an example process for processinga user order for an item, according to some implementations.

FIG. 10 is a flow diagram illustrating an example process for fillingand travel of a transportation vehicle, according to someimplementations.

FIG. 11 is a flow diagram illustrating an example process for anautonomous ground vehicle travelling to location, according to someimplementations.

FIG. 12 is a flow diagram illustrating an example process fordetermining a stopping location, according to some implementations.

FIG. 13 is a flow diagram illustrating an example process for apositioning of an autonomous ground vehicle relative to other autonomousground vehicles at a location, according to some implementations.

FIG. 14 is a flow diagram illustrating an example process for a removalof an item from a storage compartment of an autonomous ground vehicle,according to some implementations.

FIG. 15 is a flow diagram illustrating an example process for anautonomous ground vehicle delivering a storage compartment portion to alocation, according to some implementations.

FIG. 16 depicts a block diagram illustrating various components of anautonomous ground vehicle control system, according to animplementation.

FIG. 17 is a block diagram of an illustrative implementation of a serversystem that may be used with various implementations.

While implementations are described herein by way of example, thoseskilled in the art will recognize that the implementations are notlimited to the examples or drawings described. It should be understoodthat the drawings and detailed description thereto are not intended tolimit implementations to the particular form disclosed but, on thecontrary, the intention is to cover all modifications, equivalents andalternatives falling within the spirit and scope as defined by theappended claims. The headings used herein are for organizationalpurposes only and are not meant to be used to limit the scope of thedescription or the claims. As used throughout this application, the word“may” is used in a permissive sense (i.e., meaning having the potentialto), rather than the mandatory sense (i.e., meaning must). Similarly,the words “include,” “including,” and “includes” mean “including, butnot limited to.”

DETAILED DESCRIPTION

This disclosure describes a system in which autonomous ground vehicles(“AGVs”) are utilized to transport items to specified locations (e.g.,user's residences, etc.). In various implementations, transportationvehicles (e.g., delivery trucks, etc.) may be utilized to transport theAGVs and/or items for delivery, etc. A management system may beconfigured to communicate (e.g., wirelessly) with the transportationvehicles and/or AGVs. In various implementations, the general activitiesof the transportation vehicles and/or AGVs (e.g., related to thedelivery and/or receiving of items, the travel to and from thedesignated delivery and/or receiving areas, etc.) may be coordinated bythe management system. For example, the management system may receiveand/or determine schedule data for the travel of the transportationvehicles to and from the designated areas that include the locationswhere the AGVs will deliver and/or receive the items. In variousimplementations, the management system may also receive tracking data(e.g., GPS) regarding the locations of the transportation vehiclesand/or AGVs and use that data for various purposes (e.g., statusmonitoring, answering location status requests, sending notificationsregarding the current location of the transportation vehicles and/orAGVs, etc.)

In various implementations, AGVs may be transported by, and deploy from,transportation vehicles to deliver items to delivery locations. Thetransportation vehicles may be any type of mobile machine, such as atruck, car, watercraft, aircraft, etc., and control of the mobilemachine may be manual (e.g., a driver) or automated (e.g., directly orremotely controlled by an automated system, robotic, etc.). Thetransportation vehicles may also transport other types of autonomousvehicles (e.g., unmanned aerial vehicles (“UAVs”), etc.), which may alsodeliver items and/or may provide/receive assistance to/from the AGVs.For example, an AGV may require assistance to navigate past an obstacle(e.g., a barrier, etc.), for which another autonomous vehicle (e.g., aUAV, etc.) may engage the AGV and/or item to be delivered and assist(e.g., through flying, lifting, etc.) in navigating past the obstacle toreach the delivery location. As another example, it may be undesirablefor another type of autonomous vehicle (e.g., a UAV) to navigate (e.g.,fly) along a final portion of a travel path to a delivery location(e.g., due to undesirable noise levels, safety issues in proximity tothe delivery location, etc.) for which it may be preferred to have anAGV carry or otherwise assist the other autonomous vehicle and/or itemin reaching the delivery location.

In various implementations, AGVs may be owned by individual users and/ormay service a group of users in a given area (e.g., in an apartmentbuilding, neighborhood, etc.), and may be stationed at various types oflocations (e.g., inside or outside of user residences, common areas,etc.) and may travel out (e.g., to a street) to meet a transportationvehicle that is carrying items. For example, a notification may bereceived indicating that a transportation vehicle is expected to arriveat a designated meeting area (e.g., on a street) at a particular time.As another example, various types of sensors (e.g., image sensors, soundsensors, etc.) may be utilized to determine when a transportationvehicle is approaching an area. In response to an approachingtransportation vehicle, one or more AGVs may travel out to the meetingarea to receive items from the transportation vehicle. In oneconfiguration, a starting travel time may be established for an AGV tobegin travel toward the meeting area so that the AGV may arrive ahead ofthe transportation vehicle. The determination of the starting traveltime may be based at least in part on an estimated time of when thetransportation vehicle is expected to arrive at the meeting area.

In various implementations, AGVs may be deployed from various types offacilities (e.g., materials handling facilities, etc.) to deliver itemsto specified locations (e.g., user residences). In some instances, thedistance between the materials handling facility and the deliverylocation may be relatively long (e.g., 10 miles, 30 miles, 60 miles, ormore), for which an AGV may utilize various techniques for long-rangetravel. For example, various energy conservation and/or rechargingtechniques (e.g., solar charging, propellers for generating electricityfrom wind power, regenerating electricity from wheel motors whentravelling downhill, avoiding travel paths with large hills, etc.) maybe utilized. AGVs with such long range capabilities may also be utilizedto travel from one materials handling facility to another. In variousimplementations, strategically placed charging stations may also beutilized to increase the travel range of AGVs.

In various implementations, an AGV facility (e.g., which may be a typeof materials handling facility) may be sized so that it may be moreeasily located in compressed urban areas (e.g., to be closer to variousdelivery locations, etc.). In one implementation, an AGV facility may bethe size of, or smaller than, a 9′ by 18′ parking space, such that itmay be temporarily located in a delivery area where parking locations(e.g., within parking spaces) are available. In various implementations,an AGV facility may be a home base location for one or more AGVs and/ormay be configured to interact with and provide items to AGVs. Forexample, an AGV facility may include an item engagement mechanism (e.g.,a mechanical arm) that is capable of placing items in, and removingitems from, a storage compartment of an AGV. As another example, an AGVaccess door may be provided that is specifically sized to match theouter dimensions of an AGV, and which can only be accessed through useof a code/signal that the AGV is configured to provide/transmit.

In various implementations, AGVs may have various capabilities fornavigating to and from facilities, delivery locations, transportationvehicles, etc. For example, an AGV may include various sensors anddevices (e.g., imaging sensors, proximity sensors, GPS capabilities,etc.) to assist with navigation. In various implementations, an AGV mayalso include one or more access mechanisms to assist with opening accessbarriers (e.g., doors, gates, etc.) that the AGV may encounter on atravel path (e.g., on the way to a meeting area, delivery location,etc.). For example, an access mechanism may include a transmitter devicethat transmits a garage door opener signal to allow the AGV to open andclose a garage door for exiting and/or entering a garage. As anotherexample, a specialized door (e.g., sized to fit the AGV) may include alocking and/or opening mechanism that is triggered by an accessmechanism of the AGV. In accordance with such access techniques andother capabilities of AGVs, it will be appreciated that an item may bereceived and delivered by an AGV without requiring a user to be home. Inaddition, an AGV may receive and deliver an item when a user is busy orotherwise unavailable (e.g., when a user is on a phone call, sleeping,etc.). Items may also be received and delivered by AGVs at times thatmay be more conducive for deliveries (e.g., between 2:00 a.m. and 6:00a.m. when streets, sidewalks, parking locations, and/or other travelpathways and stopping locations may be less crowded, etc.).

In various implementations, AGVs containing ordered items may travel(e.g., from materials handling facilities, etc.) to pickup areas (e.g.,on a street, in a parking lot, inside a store, etc.) where users mayretrieve the ordered items from the AGVs. Users may be informed of thelocations of the AGVs through electronic notifications, etc. In variousimplementations, different numbers and/or configurations of AGVs may beat locations in a pickup area. For example, an AGV in a pickup area mayinclude multiple storage compartments that contain items for multipleusers, wherein each storage compartment is associated with an accesscode for a user. As another example, multiple AGVs may congregate in apickup area, wherein each AGV may contain an ordered item for adifferent user. In various implementations, the pickup areas may includevarious facilities/services for the AGVs. For example, one or morecharging stations may be included in a pickup area that enable the AGVsto recharge while they are waiting in the pickup area for users toarrive. As another example, a control station may be included in apickup area that communicates with AGVs in the pickup area (e.g., usingwired or wireless connections) and provides a central user interfacethat may be utilized by users to gain access to the storage compartmentsof the AGVs, etc.

In various implementations, when a group of AGVs is congregating in anarea (e.g., a pickup area, a meeting area for meeting a transportationvehicle, etc.), the positions of the AGVs may be coordinated so that theAGVs are in a designated order in the area. For example, when an AGVarrives or is otherwise in an area, if another AGV is determined to bepresent (e.g., utilizing various sensors of the AGVs and/or as indicatedby a management system, etc.), one or both of the AGVs may be instructedto move relative to the other according to a designated order. Invarious implementations, the designated order may be determinedaccording to various organizational methods. For example, if the AGVsare in a pickup area, the AGVs may be arranged in a configuration thatis relatively compact but which provides easy access for the users toretrieve items from the AGVs and/or for which AGVs that are expected toleave sooner may be placed closer to the ends of the configuration, etc.As another example, if the AGVs are waiting to meet a transportationvehicle, the AGVs may be arranged to be lined up in an order accordingto the delivery addresses where the AGVs will be delivering items. Asanother example, the AGVs may be arranged in an order according to anarranged order of items that are stored in a transportation vehicle. Itwill be appreciated that such arrangements of AGVs in a meeting area maysimplify a transfer of items from a transportation vehicle to the AGVs.In various implementations, the AGVs may also include markings or otheridentifying symbols or devices (e.g., flashing lights, sounds, etc.) forsimplifying the identification and transfer of corresponding items fromthe transportation vehicle and/or to assist users or agents in locatingAGVs that contain or are to receive ordered items, etc.

In various implementations, stopping locations (e.g., places wheretransportation vehicles may park or otherwise stop to deploy or meetAGVs, places where AGVs may stop/congregate to meet transportationvehicles, etc.) may be planned and/or determined in various ways. Forexample, if a previously planned stopping location is not available, orif a stopping location has not yet been planned, a transportationvehicle and/or AGVs may search for stopping locations. As anotherexample, a management system may assist with a search for stoppinglocations. Once one or more available stopping locations have beenfound, an evaluation process may be performed to determine if thestopping locations meet certain criteria. For example, if atransportation vehicle will be stopping (e.g., parking) at a stoppinglocation from which AGVs will be deployed, the stopping location mayrequire sufficient room for the transportation vehicle to park and to bein an orientation from which the AGVs can be safely deployed (e.g., outof a back or side of the transportation vehicle, etc.), and may requireenough room adjacent to the stopping location for the AGVs as they aredeployed or wait (e.g., on a sidewalk that is not currently crowded,etc.). Similarly, if AGVs will be meeting (e.g., and waiting for) thetransportation vehicle, the AGVs may require stopping locations (e.g.,on a sidewalk, etc.) that will be proximate to the transportationvehicle, and where the AGVs can safely wait for and/or interact with thetransportation vehicle once it arrives. As another example, if a user isto meet an AGV at a stopping location (e.g., in a pickup area where auser is informed of the location of the AGV and meets the AGV foracquiring an ordered item), the stopping location may need to be at alocation where the AGV can safely wait for the user (e.g., to the sideof a sidewalk, or otherwise in a space that is not in the way of otheractivities or pathways of travel for other entities), and where the usercan easily find and interact with the AGV, etc.

In various implementations, the AGVs may be modular in that a storagecompartment portion (e.g., which may hold an ordered item) may beremovable (i.e., separable) from a propulsion portion. In variousimplementations, the storage compartment portion may be securelyattached to the propulsion portion during transport (e.g., requiring anaccess code to remove and/or open), and the storage compartment portionmay similarly be securely attached to the delivery location (e.g., at adocking station) when delivered. For example, coupling portions (e.g.,for mechanical and/or electronic coupling) may be utilized for couplingthe storage compartment portion to the propulsion portion and/or adocking station. In some configurations, storage compartment portionsmay also include coupling portions for mechanically and/orelectronically coupling to one another. In various implementations, thestorage compartment portion may be refrigerated, heated, etc., and mayinclude various sensors on the inside and outside of the storagecompartment portion (e.g., temperature sensors, motion sensors, imagesensors to determine the presence and condition of items and/or toassist with navigation and other operations of the propulsion portion,etc.).

As used herein, a “materials handling facility” may include, but is notlimited to, warehouses, distribution centers, cross-docking facilities,order fulfillment facilities, packaging facilities, shipping facilities,rental facilities, libraries, retail stores, wholesale stores, museums,or other facilities or combinations of facilities for performing one ormore functions of materials (inventory) handling. A “delivery location,”as used herein, refers to any location at which one or more inventoryitems may be delivered. For example, the delivery location may be auser's residence, a place of business, any location where a user orinventory is located, etc. Inventory or items may be any physical goodsthat can be transported using an AGV.

A block diagram of a materials handling facility which, in oneimplementation, may be an order fulfillment facility configured toutilize various systems and methods described herein (e.g., with regardto utilization of transportation vehicles and AGVs for delivering items,etc.), is illustrated in FIG. 1. In this example, multiple users 100 maysubmit orders 120, where each order 120 specifies one or more items frominventory 130 to be shipped or otherwise delivered (e.g., by atransportation vehicle and/or AGV) to the user or to another entityspecified in the order. An order fulfillment facility typically includesa receiving operation 180 for receiving shipments of stock from variousvendors and storing the received stock in inventory 130. To fulfill theorders 120, the item(s) specified in each order may be retrieved or“picked” from inventory 130 (which may also be referred to as stockstorage) in the order fulfillment facility, as indicated by pickingoperation 140. The picking operation 140 may in various implementationsbe manual or automated (e.g., robotic). In some implementations, theitems of a user order may be divided into multiple shipment sets forfulfillment by a planning service before fulfillment instructions aregenerated (not shown). As used herein, the term “shipment set” may referto a single item of a user's order, multiple items of a user's order, orall items of a user's order.

In some instances, when a transportation vehicle and/or AGV has beendesignated for a delivery, the item(s) of one or more shipment sets maybe picked at the picking operation 140 directly into storage areas(e.g., bins) of the transportation vehicle and/or storage compartmentsof AGVs and/or other autonomous vehicles (e.g., which may be carried bythe transportation vehicle or may travel independently, etc.). Invarious implementations, the item(s) in a particular storage area of thetransportation vehicle may be designated for further transport by aparticular AGV, as will be described in more detail below with respectto FIGS. 3-4. More specifically, once the transportation vehicle reachesa designated location, the item(s) in a particular storage area may befurther transported by an AGV to a location (e.g., a delivery locationat a user's residence, a stopping location in a pickup area, etc.). Insome implementations, the storage areas of the transportation vehiclemay be permanently affixed within the transportation vehicle. In otherimplementations, the transportation vehicle may include removablecomponents that may be filled with items and/or AGVs in the materialshandling facility and then placed in the transportation vehicle. Forexample, a storage area of a transportation vehicle may include a bay ofbins, which may remain in the transportation vehicle or may be removedand filled with items and/or AGVs inside a materials handling facility,after which the bay of bins may be moved back into the transportationvehicle for transport. Regardless of whether the storage areas of thetransportation vehicle are fixed or removable, it will be appreciatedthat by picking items directly into the storage areas of thetransportation vehicle and/or storage compartments of the AGVs, theitems may not need to be packed in shipping packages. In addition, thepacking slip typically included in a shipping package may be applied tothe item (e.g., stickered to the item), printed out at thetransportation vehicle and/or AGV upon retrieval of the item, orotherwise made available to a user.

In various implementations, the storage areas of the transportationvehicles and/or storage compartments of the AGVs may each include aunique identifier, such as a bar code, QR code, unique number, etc., toenable tracking, identification, and/or association of items placed ineach of the storage areas and/or storage compartments. For example,during a picking operation, an agent or automated system (e.g., robotic)within the materials handling facility may scan the bar code of thestorage area or storage compartment and/or scan a bar code or identifierof the picked item as the item is picked and/or placed into the storagearea or storage compartment. Scanning of the storage area or storagecompartment and/or the picked item may be utilized to associate andtrack the item with the storage area and the transportation vehicle orthe storage compartment and the AGV. As storage areas of transportationvehicles and/or storage compartments of AGVs are filled, a routingoperation 145 may route the filled storage areas, transportationvehicles, storage compartments, and/or AGVs to an appropriatetransporting operation 155 from which the transportation vehicle and/orAGV may travel to a designated location, as will be described in moredetail below with respect to FIGS. 3-8.

In other examples, a transportation vehicle (e.g., a truck) and/or anAGV may be made to hold or otherwise transport one or more deliverycontainers, in which case the item(s) of one or more shipment sets maybe picked at the picking operation 140 directly into deliverycontainers. A “delivery container,” as used herein, may be any form ofcontainer used in transporting or handling items. For example, adelivery container may be a tote, pallet, bin, trailer, etc.Additionally, the delivery container may be segmented or otherwiseinclude division points, permanent or movable, that enable separation ofitems within the delivery container. In some instances, itemsthemselves, such as larger items (e.g., big screen televisions, desks,cabinets) may be considered and treated as delivery containers. Thedelivery container may also include a unique identifier, such as a barcode, QR code, unique number, etc., to enable tracking andidentification of the delivery container and association of items placedinto the delivery container. For example, during a picking operation, anagent within the materials handling facility may scan the bar code ofthe delivery container and scan a bar code or identifier of the pickeditem as the item is placed into the delivery container. Scanning of thedelivery container and the picked item results in the item becomingassociated with and tracked with the delivery container. In someimplementations, for delivery containers that are segmented or otherwiseinclude division points, those segments may each include a uniqueidentifier (e.g., bar code) and as items are placed in the deliverycontainer they may be associated with a specific location, or segmentwithin the delivery container by scanning the identifier of thatsegment. Likewise, because items may not be packed in shipping packages,the packing slip typically included in a shipping package may be appliedto the item (e.g., stickered to the item), printed out at thetransportation vehicle and/or AGV when the item is transferred ordelivered, or otherwise made available to a user.

Regardless of the type of delivery container utilized, in someimplementations, some types of items can be transported in the deliverycontainer without needing to be packed in a shipping package inside thedelivery container. In other instances, items that are eitherpre-packaged, fragile, or need additional protection prior to transportmay be picked and packed in a shipping package. In anotherimplementation, items may be put into bags prior to placement in thedelivery container and/or storage areas to provide confidentiality ofthe ordered items. In addition, items from multiple shipment sets to betransported by the same transportation vehicle and/or AGV may be pickedinto the same delivery container for transport. As delivery containersare filled, a routing operation 145 may route the filled deliverycontainers to the appropriate transporting operation 155 for placementin a designated transportation vehicle and/or AGV. The routing operation145 may be manual or automated. The routing operation 145 may receive anindication of the transportation vehicle and/or AGV to which each itemshould be routed from a shipment planning system and route deliverycontainers to an appropriate transporting operation 155, from which theymay be placed in a designated transportation vehicle and/or AGV.

In other examples, some picked items may be delivered to one or morestations in the order fulfillment facility for sorting 150 into theirrespective shipment sets and for packing 160 in shipping packages. Apackage routing operation 165 may sort orders for packing in shippingpackages to one of two or more shipping operations 170, from which theymay be shipped to the users 100. In various implementations,transportation vehicles and/or AGVs may be utilized for the shipping andmay be considered as an alternative to shipping by traditional carriers.The package routing operation 165 may, depending on the specificimplementation, be either automated or manual. The package routingoperation 165 may receive an indication of the destination to which eachpacked shipment set should be routed from a central control system. Insome instances, the destination may be the final destination identifiedby the user, or a destination at which transfer of a shipment set mayoccur for final delivery to the user, or a location from which one ormore AGVs may complete the final delivery. The package routing operation165 may also determine a routing destination for each packed shipmentset dependent on the size of a shipping package in which the shipmentset is contained and/or based on whether the shipment set will bedelivered by a traditional carrier, a transportation vehicle, and/or anAGV.

The arrangement and order of operations illustrated by FIG. 1 is merelyone example of many possible implementations of the operation of amaterials handling facility, such as an order fulfillment facility, thatenables filling of transportation vehicles and/or AGVs with items andsubsequent transportation of the items (FIGS. 3-8) and/or otherfulfillment of user orders. Other types of materials handling,manufacturing, or order fulfillment facilities may include different,fewer, or additional operations and resources, according to differentimplementations.

FIG. 2A depicts a block diagram of a side view of an AGV 200A, accordingto an implementation. In the example of FIG. 2A, the AGV 200A includes astorage compartment portion 202A and a propulsion portion 201A. Thepropulsion portion 201A includes four wheels 222 which are mounted onaxles 224 that may be rotated by one or more motors 220 of a propulsionsystem of the propulsion portion 201A. In other implementations,additional or fewer motors 220 and/or wheels 222 may be included in thepropulsion portion 201A. The size of the AGV 200A may vary and, forpurposes of illustration with respect to the example of FIG. 2A, thestorage compartment portion 202A may include a storage compartment 257which may hold items that are transported by the AGV 200A. In variousimplementations, the storage compartment 257 may be divided into smallerstorage compartments (e.g., storage compartments 257A and 257B, as willbe described in more detail below with respect to FIG. 2B).

In various implementations, varying numbers and/or sizes of storagecompartments, and/or additional features may be included depending onthe specific implementation. The shape of the AGV 200A may also vary,depending on the implementation. For example, the AGV 200A may be sizedand shaped to be drivable on a standard sidewalk or road, and to fitwithin a doorway or other access point (e.g., of a user's residence,etc.). The storage compartment 257 may be sized according to variousfactors (e.g., to match the size of a standard bin of a materialshandling facility, wherein similar sized bins may also be used on thetransportation vehicles that bring the items to the AGVs, as well as inthe materials handling facilities that the items are transported from,etc.). In various implementations, the utilization of standard sized andconfigured bins (e.g., with a scanning code in a standard location,etc.) may simplify the transfers and processing of items. For example,ordered items that are placed in a standard sized bin at a materialshandling facility may be easily transported by a transportation vehicleand/or AGV that is configured for transporting and processing thestandard sized bin, resulting in greater efficiencies throughout theoverall transportation process. In various implementations,weatherproofing techniques may be utilized to protect the functionalityof the AGV 200A and any operational components (e.g., storagecompartments, control panels, etc.) when the AGV 200A is subjected toweather conditions during travel and/or other operations. The AGV 200Afurther includes an AGV control system 210, which as discussed infurther detail below with respect to FIG. 16, may control the operation,routing, navigation, communication, object sense and avoid, itemengagement mechanism, etc. of the AGV 200A.

As shown in FIG. 2A, various sensors 204 may be mounted to the AGV 200A.For example, sensors 204-1 and 204-2 may be mounted on the front andback of the AGV 200A, respectively. The sensors 204 may be of varioustypes. In general, certain sensors 204 may be utilized to assist withthe navigation, object sense and avoid, etc. of the AGV 200A. Forexample, the sensors 204-1 and/or 204-2 may include imaging sensorsand/or distance detection sensors for measuring and monitoring thedistance between the AGV 200A and other objects (e.g., an obstacle, aroadway, another AGV, etc.). While the example illustrated in FIG. 2Aincludes two sensors 204 mounted to the AGV 200A, in otherimplementations, fewer or additional sensors may be utilized. In oneimplementation, each of the sensors 204-1 and 204-2 may berepresentative of an array of sensors that are utilized to assist withthe various functions of the AGV 200A.

The AGV 200A also includes one or more power modules 212. In thisexample, the AGV 200A includes a power module 212 that is removablymounted at the bottom of the AGV 200A in the propulsion portion 201A.The power module 212 for the AGV 200A may be in the form of batterypower, solar power, gas power, super capacitor, fuel cell, alternativepower generation source, or a combination thereof. The power module 212is coupled to and provides power for the AGV control system 210 and themotor(s) 220 of the propulsion portion, as well as any other attachedinput/output devices, etc. The power module 212 stores energy with acorresponding energy level. In various implementations, the storedenergy level of the power module 212 may be recharged through varioustechniques. For example, as will be described in more detail below, whenan AGV is at a home base location or other location, the AGV 200A mayengage with a charging station that will recharge the power module. Asanother example, an AGV may also or alternatively utilize othertechniques for recharging (e.g., utilizing sunlight to recharge throughsolar panels, etc.). In addition, in some implementations, a powermodule may be configured such that it can be autonomously removed and/orreplaced with another power module while the AGV 200A is at a home baselocation or other location.

In various implementations, the AGV 200A may also include an itemengagement mechanism (not shown). For example, the item engagementmechanism may include a robotic arm or other mechanism that may beutilized to engage an item for placement in a storage compartment 257 ofthe AGV 200A, or for removing an item from a storage compartment 257when the item is being delivered to a delivery location. The itemengagement mechanism may communicate with (via wired or wirelesscommunication) and be controlled by the AGV control system 210. Invarious implementations, such item engagement mechanisms may also oralternatively be included in a transportation vehicle, home baselocation, meeting area, user's residence, etc. for placing items inand/or removing items from a storage compartment 257 of the AGV 200A.

The AGV control system 210 maintains information as to whether a storagecompartment of the AGV 200A is empty or includes items, the accesscode(s) or other identifier(s) necessary to open the storage compartmentand any other information necessary to maintain the AGV. The AGV controlsystem 210 may also lock/unlock storage compartments, activate sensors,and the like. The AGV 200A may be configured to obtain information froma remote computing resource or may be configured to operate primarily asa stand-alone unit, with limited external communication toreceive/provide order/delivery/transfer information. FIG. 3, describedbelow, illustrates an example of an environment in which a managementsystem 326 is provided for remotely communicating with an AGV 200A aspart of a system for transporting items. The AGV control system 210 mayinclude a component configured to provide wired and/or wireless networkconnectivity (e.g., with computing resources in a user device, remotecomputing resources, etc.). Wireless connectivity may be implementedusing a wireless antenna (not shown), which may provide both receive andtransmit functionality.

The AGV 200A may also include a user interface 211. The user interface211 is configured to receive and provide information to a user of theAGV 200A and may include, but is not limited to, a display, such as atouch-screen display, a scanner, a keypad, a biometric scanner, an audiotransducer, one or more speakers, one or more image capture sensors,such as a video camera, and any other types of input or output devicesthat may support interaction between the AGV 200A and a user. In variousimplementations, the user interface 211 may alternatively include morelimited features. For example, in one implementation the user interface211 may only include a relatively small display and/or a keypad forproviding input. In certain other implementations, these and otherfeatures may also be eliminated, wherein control of the AGV 200A mayprimarily be provided remotely. For example, in order to access astorage compartment, a user may send or reply to a text message to orfrom a centralized remotely located control system (e.g., a managementsystem), which controls the AGV 200A to open the storage compartmentdoor so that the user can retrieve an ordered item. In variousimplementations, the AGV 200A may have capabilities for directlyreceiving such signals from a user device or other device (e.g., adevice inside a user's residence) that provides a signal to open thestorage compartment door.

In the example of FIG. 2A, the storage compartment 257 of the storagecompartment portion 202A of the AGV 200A includes bottom and sidesurfaces and a door 275 configured to form a cavity in which items maybe stored. In addition, the storage compartment 257 may include varioussecurity or other components. For example, the storage compartment 257may include a locking mechanism 277, which may be controlled directly orremotely by the AGV control system 210. The storage compartment 257 mayalso include a presence detection sensor 271, a motion sensor 272, animage capture sensor 273, a temperature sensor 274 and/or other sensors.

In various implementations, the locking mechanism 277 may be controlledby the AGV control system 210, either through wired or wirelesscommunication, to effect locking and unlocking of a door 275 of astorage compartment 257. For example, when a user, carrier, etc.interacts with the user interface 211 (e.g., via the display, or with auser device, etc.) and provides an access code or other identifier, theAGV control system 210 may unlock the storage compartment 257. In aconfiguration in which the locking mechanism 277 includes a pin holdingthe door closed, the AGV control system 210 may activate the lockingmechanism 277 such that the pin retracts, thereby disengaging the lockof the storage compartment 257 allowing the door 275 as mounted on ahinge 276 to open. In some implementations, the storage compartment 257may also include a spring mechanism (not shown) such that when thelocking mechanism 277 is disengaged, the spring mechanism propels thedoor 275 outward, thereby identifying to a user, carrier, etc. that thedoor 275 is unlocked and the storage compartment 257 is accessible.

In addition to the use of retractable pins, any mechanical, magnetic,electrical or other form of locking mechanism may be utilized with thevarious implementations described herein. In addition, the storagecompartment 257 may also include magnets to help close a door. Moreover,while the above example describes the AGV control system 210 controllingthe locking mechanism, in other implementations, the storage compartmentmay also or alternatively be controlled and/or communicated withdirectly by a command component and/or remote computing resources, etc.

The presence detection sensor 271 may be used to detect the presence orabsence of objects in the storage compartment 257, and the motion sensor272 may be used to detect movement in the storage compartment 257. Forexample, the presence detection sensor 271 may be utilized when anagent, carrier, user, or automated system (e.g., robotic) is placingitems, delivery containers and/or transfer containers in the storagecompartment 257 to confirm that the item is indeed in the storagecompartment 257 before the door 275 is closed and locked by the lockingmechanism 277. Additionally, the presence detection sensor 271 and/ormotion sensor 272 may also be used when a user is retrieving an itemstored in the storage compartment 257 or when a carrier is adding orremoving an item, delivery container and/or transfer container from thestorage compartment 257. For example, when a user interacts with theuser interface 211 or an access code is otherwise provided such that astorage compartment 257 is opened, the presence detection sensor 271and/or motion sensor 272 may be used to confirm that a user has reachedinto the storage compartment 257 and removed its contents (or addeditems in the case of returns). In some implementations, there may bemultiple presence detection sensors 271 and/or motion sensors 272distributed throughout the inside of a storage compartment to ensureobjects/motion is detected.

The storage compartment 257 may also include an image capture sensor273, such as a camera, and optionally an illumination component (notshown), such as a light emitting diode (LED), that may be used toilluminate the inside of the storage compartment 257. The image capturesensor 273 may also be used to capture images or and/or detect thepresence or absence of items within the storage compartment 257. Forexample, the image capture sensor 273 may be used to capture images toidentify the type of object located within the storage compartment 257and/or to identify or record video/images of access within the storagecompartment 257. In various implementations, the sensor 273 and/or aseparate item identification sensor may include a bar code scanner orother technology that is utilized to determine an identification of anitem that is being placed, or has been placed, in the storagecompartment 257. For example, a sensor including a bar code scanner orother identification technology may be located with or as part of theother sensors 271-274, on the door 275, as part of the user interface211, or otherwise positioned so as to scan or otherwise identify an itemas it is being placed or is otherwise within the storage compartment257. Such identification and/or images, video etc. may be recorded bythe system and/or transmitted (e.g., to a management system as will bedescribed in more detail below with respect to FIG. 3) and/or may beprovided to a user to identify what items have been placed in a storagecompartment for delivery. For example, a user may wish to receive amessage and/or image indicating what items are being delivered.

Some storage compartments 257 may be refrigerated storage compartments.In various implementations, such refrigerated storage compartments mayinclude their own cooling mechanisms and/or the AGV 200A may have acentralized cooling system. The temperature of previouslynon-refrigerated storage compartments may be adjusted to becomerefrigerated storage compartments, and vice versa. In an implementationwith multiple refrigerated storage compartments, the temperature in eachof the refrigerated storage compartments may be separately adjustable,such that items inside each of the refrigerated storage compartments maybe cooled to a desired temperature. For example, items that need to bechilled or frozen at specified temperatures, such as groceries ormedical supplies, may be stored in refrigerated storage compartments.

In various implementations, the temperatures in the refrigerated storagecompartments may be adjusted when items are to be placed into therefrigerated storage compartments, or may be adjusted in advance. Forexample, when a refrigerated item is scheduled to be placed into arefrigerated storage compartment of an AGV, the temperature of therefrigerated storage compartment may be adjusted to a temperature thatis specified for the refrigerated item in advance so that therefrigerated storage compartment will already be at the specifiedtemperature when the item is placed into the refrigerated storagecompartment. In one implementation, the image capture sensor 273 may beused to capture an image of an item when it is placed into a storagecompartment in order to try to determine an appropriate storagetemperature for the item. For example, an item may have information on alabel which identifies a storage temperature, such as “contents to bestored at 32 degrees F. or lower.”

The temperatures in some or all of the refrigerated storage compartmentsmay be controlled by the AGV control system 210. Continuous monitoringand regulating of the temperatures of the refrigerated storagecompartments in which such items are kept may be important for verifyingthe condition of the items. Temperature sensors, such as the temperaturesensor 274 of the storage compartment 257, may be utilized for sensingthe temperature for monitoring and regulating the temperature inside therefrigerated storage compartment. The refrigerated storage compartmentand/or the entire AGV 200A may be insulated to prevent the dissipationof the cooled air from the refrigerated storage compartment.

In various implementations, a refrigerated storage compartment may be aninsulated storage compartment which is cooled by passive coolingelements that are placed within the storage compartment. For example,rather than utilizing an active cooling system which may have componentssuch as compressors and coils, the storage compartment may be cooled bypassive cooling elements such as cold packs, frozen water bottles, etc.In one implementation, the passive cooling elements may be added to thestorage compartment when the item is first placed into the storagecompartment, such as at a meeting area. In another implementation, thepassive cooling elements may be included in a shipping container with anitem at a materials handling facility when it is shipped to be deliveredby an AGV. In an alternative implementation, the passive coolingelements may be added to the insulated storage compartment with the itemwhen it arrives or is otherwise placed in the storage compartment.

In various implementations, the number of passive cooling elements to beincluded with an item may be calculated based on a number of factors.For example, one factor may be an estimated maximum period of time thatthe item may remain in the storage compartment before it is retrieved bya user. Another factor may be the expected ambient temperature aroundthe AGV and/or during transport. Other factors may include the size ofthe storage compartment, the size and number of items to be included inthe storage compartment, etc. Various government regulations may alsospecify temperatures at which certain items are to be maintained. Forexample, various federal, state and/or municipal regulations may dictaterequirements for storage temperatures for items as well as maximumperiods of time that items may be stored at a given temperature. All ofthese factors may be included in a calculation of how many passivecooling elements should be included in an insulated storage compartmentwith an item, as well as a determination of a maximum period of timethat the item may remain in the storage compartment.

In various implementations, the AGV 200A may also include a locatordevice (not shown) that is configured to assist with finding the AGV(e.g., when a transportation vehicle is searching for an AGV which is toreceive an item, when a user is wanting an update on the location of anAGV that is delivering an item, etc.). For example, the locator devicemay wirelessly transmit an electronic signal that enables the positionof the AGV to be tracked and/or otherwise determined (e.g., as indicatedon a screen of a mobile electronic device, etc.). As another example,the locator device may emit various sounds, activate lights, etc. (e.g.,to assist a carrier who is delivering items to multiple AGVs todetermine which AGV is the correct AGV for a current item). In variousimplementations, the locator device may be controlled by the AGV controlsystem 210 and/or a management system (FIG. 3), etc. In variousimplementations, the AGV 200A may also include an RFID tag, a printedcircuit board, or any other object or mechanism that may be detectableand used to identify the AGV 200A for security or other purposes (e.g.,by a transportation vehicle, at an access point into a user's residence,etc.).

In various implementations, the AGV 200A may be modular in that thestorage compartment portion 202A may be removable (i.e., separated) fromthe propulsion portion 201A. For example, when the storage compartmentportion 202A is coupled to the propulsion portion 201A, a lower surface231S of the storage compartment portion 202A may be in contact with anupper surface 231P of the propulsion portion 201A. Various couplingportions 236 and 238 may be included for coupling the storagecompartment portion 202A to the propulsion portion 201A. For example,the storage compartment portion 202A may include coupling portions236-1S, 236-2S and 238-S, which may couple to corresponding couplingportions 236-1P, 236-2P and 238-P, respectively, of the propulsionportion 201A. In various implementations, each of the coupling portions236 and 238 may be utilized for electronic coupling and/or mechanicalcoupling (e.g., latching, locking, etc.).

In various implementations, the coupling portion 238S and/or 238P mayinclude electronic coupling portions for electronically coupling thestorage compartment portion 202A to the propulsion portion 201A. Forexample, either of the coupling portions 238S or 238P may consist ofwired male/female electronic coupling portions (e.g., which may coupletogether), and/or one or both of the coupling portions 238S or 238P mayinclude a wireless coupling portion that transmits signals forwirelessly coupling the storage compartment portion 202A to thepropulsion portion 201A and/or to other systems (e.g., the managementsystem 326 of FIG. 3). In various implementations, the electroniccomponents of the storage compartment portion 202A (e.g., electroniccomponents 204, 211, 271-274, 277, etc.) may be coupled to the controlsystem 210 and power supply 212 of the propulsion portion 201A throughthe coupling portions 238S and/or 238P which thereby enable electroniccommunication between the electronic components of the storagecompartment portion 202A and the control system 210. In variousimplementations, the coupling portion 238S may also include a controlsystem, power module and/or other electronic components of the storagecompartment portion 202A (e.g., which may perform similar functions asthe control system 210 and power module 212 of the propulsion portion201A). In such a configuration, certain electronic functions of thestorage compartment portion 202A and/or the individual electroniccomponents 204, 211, 271-274 may continue to operate after the storagecompartment portion 202A and the propulsion portion 201A are separated.For example, the user interface 211 may continue to operate (e.g., toenable interaction with a user, to allow an access code to be enteredfor unlocking the locking mechanism 277 to enable the storagecompartment 257 to be opened, etc.).

In various implementations, the coupling portions 236-1S, 236-2S, 236-1Pand/or 236-2P may include mechanical coupling elements (e.g., latches,magnetic, locks, etc.) for physically connecting/attaching the storagecompartment portion 202A to the propulsion portion 201A. For example,the coupling portions 236-1S, 236-2S, 236-1P and/or 236-2P may includelocking mechanisms for locking the storage compartment portion 202A tothe propulsion portion 201A. In such a configuration, an access code(e.g., as provided on the user interface 211 and/or as otherwiseprovided to the control systems 210 or 238S, etc.) may be required tounlock the locking mechanisms to allow the storage compartment portion202A to be decoupled (e.g., unlocked, released, separated, etc.) fromthe propulsion portion 201A.

The storage compartment portion 202A may also include a coupling portion205S and/or the propulsion portion 201A may also include a couplingportion 205P, each of which may include various electronic and/ormechanical coupling elements. In various implementations, the couplingportions 205S and/or 205P may be utilized to electronically and/ormechanically couple the storage compartment portion 202A and/or thepropulsion portion 201A to other systems/components (e.g., a dockingstation, a charging station, other AGVs, a control station in a pickuparea, etc.). For example, at a user's residence, the coupling portion205S and/or 205P may be utilized to attach/lock/couple the storagecompartment portion 202A and/or the propulsion portion 201A to a securestructure (e.g., as part of the user's residence and/or a dockingstation, etc.), which may also provide recharging and/or electroniccommunication capabilities. As another example, at a meeting and/orpickup area, the coupling portion 205S and/or 205P may be utilized toattach/lock/couple the storage compartment portion 202A and/or thepropulsion portion 201A to another AGV and/or control station, etc., forsecurity, communication, recharging, etc. In configurations wherestorage compartment portion 202A and propulsion portions 201A areseparated, the coupling portions 205S enable different storagecompartment portions to be mechanically and/or electronically coupledtogether, while the coupling portions 205P enable different propulsionportions to be mechanically and/or electronically coupled together(e.g., for group charging, communications, security, etc.). It will beappreciated that while the coupling portions 205S and 205P are onlyillustrated on one side of the AGV 200A in the example of FIG. 2A, thatin various implementations multiple such coupling portion 205S and 205Pon multiple sides of an AGV may be included (e.g., for coupling to otherAGVs and/or control stations, etc. on opposite sides of the AGV, etc.).

The storage compartment portion 202A and/or the propulsion portion 201Amay also include movement mechanisms 234-1 and/or 234-2 (e.g., automatedmovement mechanisms including rollers, a mechanical actuator, a roboticarm, etc.). In various implementations, the movement mechanisms 234-1and/or 234-2 may be utilized to assist with the movement of the storagecompartment portion 202A relative to the propulsion portion 201A. Forexample, if the storage compartment portion 202A is to bedetached/removed from the propulsion portion 201A (e.g., to be deliveredto a location), the movement mechanisms 234-1 and/or 234-2 may beutilized to detach and/or move (e.g., roll) the storage compartmentportion 202A off of the propulsion portion 201A at the location (e.g.,to be placed on a porch at a user's residence, to be coupled to adocking station at the location, etc.). Once the storage compartmentportion 202A has been separated from the propulsion portion 201A, thepropulsion portion 201A may navigate along a travel path away from thelocation where the storage compartment portion 202A has been left.

As another example, when a storage compartment portion 202A is to becoupled to a propulsion portion 201A (e.g., the propulsion portion 201Ais picking up the storage compartment portion 202A from a location), themovement mechanisms 234-1 and/or 234-2 may be utilized to move (e.g.,roll) the storage compartment portion 202A onto the propulsion portion201A and/or to a proper coupling position on top of the propulsionportion 201A (e.g., where the coupling portions 236 and 238 arerespectively coupled). In various implementations, certain locations mayhave elevated structures (e.g., as part of docking stations, etc.) thatare approximately level with the top surface 231P of the propulsionportion 201A, and on which the storage compartment portion 202A may bemade to rest when it is not coupled to the propulsion portion 201A. Forexample, a docking station may include such an elevated surface, whereinas the storage compartment portion 202A is moved (e.g., rolled, slide,etc.) off of the propulsion portion 201A, it will slide or otherwise beplaced on the elevated surface (e.g., and may be positioned such thatthe coupling portions 205, 236 and/or 238 of the storage compartmentportion 202A are made to couple to corresponding coupling portions ofthe docking station, etc.). In one implementation, such an elevatedsurface may include a pair of forked surfaces that slide into formedopenings (not shown) between the storage compartment portion 202A andthe propulsion portion 201A, and which enable the propulsion portion201A to move beneath the storage compartment portion 202A while it restson the elevated surface.

In various implementations, the AGV 200A may include a solar chargingmechanism 278 (e.g., including one or more solar panels, etc.) toreceive sunlight (e.g., to recharge the power module 212, provide powerto the propulsion portion 201A, provide power to certain sensors, etc.).In various implementations, the orientation of the solar chargingmechanism 278 may be adjustable (e.g., as controlled by one or moremovement mechanisms and moved separately from the door 275, etc.)relative to the orientation of the propulsion portion 201A (e.g., so asto be adjustable toward the sunlight, etc.). In various implementations,in addition to being included above the door 275 of the AGV 200A, asolar charging mechanism may be included on and/or extendable (e.g.,utilizing hinges, foldable portions, extendable arms, etc.) from one ormore alternative and/or additional surfaces of the AGV 200A. Forexample, the solar charging mechanism 278 may be included on and/orextendable from a side or bottom surface of the storage compartmentportion 202A, and/or may be included on and/or extendable from a surfaceof the propulsion portion 201A, etc. In various implementations, otherconfigurations of AGVs may similarly include solar charging mechanisms(e.g., including the configurations of FIGS. 2B and 2C, as will bedescribed in more detail below).

FIG. 2B depicts a block diagram of a side view of another AGV 200B,according to an implementation. The AGV 200B of FIG. 2B is similar tothe AGV 200A of FIG. 2A, and includes a storage compartment portion 202Band a propulsion portion 201B. One difference of the AGV 200B is thatthe storage compartment 257 has been divided into storage compartments257A and 257B. The components of the storage compartments 257A and 257Bare similar to those of the storage compartment 257, and will beunderstood to operate similarly, except as otherwise described below.More specifically, the storage compartments 257A and 257B each includerespective doors 275A and 275B on hinges 276A and 276B, as well asrespective locking mechanisms 277A and 277B. The storage compartments257A and 257B also each include respective sets of sensors 271A-274A and271B-274B.

In various implementations, the two storage compartments 257A and 257Bmay allow the AGV 200B to securely transport different items fordifferent user orders and/or to have a separate storage compartment fordifferent environmental or other needs (e.g., one of the storagecompartments may be refrigerated, etc.). For example, an AGV may receiveitems from a transportation vehicle that are to be delivered to twodifferent delivery locations as separately stored in the storagecompartments 257A and 257B. In such a configuration, the AGV may travelto a first delivery location to deliver the item(s) that are stored inthe storage compartment 257A, and then travel to a second deliverylocation to deliver the item(s) that are stored in the storagecompartment 257B. A separate access code or other mechanism may beutilized for opening each of the storage compartments, so that each usermay only access or otherwise receive the item(s) that are part of theirdelivery As another example, an AGV may receive items from two differenttransportation vehicles or other sources, wherein the item(s) from onesource may be stored in the storage compartment 257A while the item(s)from another source may be stored in the storage compartment 257B,before the AGV delivers the multiple items to one or more deliverylocations.

In various implementations, a transfer mechanism (e.g., an automatedmechanism including rollers, a robotic arm, etc.), which may be a typeof item engagement mechanism, may also be included that allows items tobe transferred from one storage compartment to another. For example, apartition between the storage compartments 257A and 257B may be movableand/or may otherwise have an access point or other mechanism to enable atransfer mechanism to move an item from storage compartment 257A tostorage compartment 257B, or vice versa. In various implementations,items may be moved between storage compartments for various purposes.For example, if the AGV includes multiple items in the storagecompartment 257A that are to be delivered to different locations, atransfer mechanism may be utilized to move the corresponding items for arespective delivery to the storage compartment 257B (e.g., wherein theuser at the delivery location will only be given access to the storagecompartment 257B that contains the ordered items). As another example,the AGV may receive items from multiple different transportationvehicles or other sources, wherein the item(s) from each source mayinitially be placed in the empty storage compartment 257B before beingmoved by a transfer mechanism to be secured within the storagecompartment 257A before additional items are received from anothersource in the storage compartment 257B. In such a configuration, if theitems are all being delivered to a single delivery location, access tothe storage compartment 257A may be provided at the delivery location.Alternatively, if the items are being delivered to multiple deliverylocations, for each respective delivery the transfer mechanism may beutilized to move the corresponding items for the respective delivery tothe storage compartment 257B, as described above.

In various implementations, a transfer mechanism may also be utilizedfor transferring items between AGVs. For example, doors or panels in thesides, etc. of the AGVs may be movable and/or may otherwise have anaccess point or other mechanism to enable a transfer mechanism to movean item from one AGV to another (e.g., as the AGVs have moved to beadjacent to one another, etc.). In various implementations, items may betransferred between AGVs for various purposes. For example, if a firstuser wishes to provide an item to a second user (e.g., without requiringhuman interaction for the transfer), the first user's AGV that containsthe item may be designated as a transportation vehicle and may travel tomeet the second user's AGV at a meeting area where the item will betransferred to the second user's AGV for subsequent delivery to thesecond user. As another example, if an item is to be transported over along distance, a first AGV that contains the item may be designated as atransportation vehicle and may travel for a first distance to meet asecond AGV at a meeting area where the item will be transferred to thesecond AGV for subsequent transport for a second distance, etc.

Another difference of the AGV 200B as compared to the AGV 200A, is thatthe storage compartment portion 202B includes a user interface 211S anda sensor 204-1S, and the propulsion portion 201B includes a userinterface 211P and a sensor 204-1P. In various implementations, byincluding such components on each of the storage compartment portion202B and the propulsion portion 201B, each of the storage compartmentportion 202B and the propulsion portion 201B may be able to betteroperate independently when they are separated. For example, theinclusion of the user interface 211P allows for user input/interactionto be received by the propulsion portion 201B when it is separated fromthe storage compartment portion 202B (e.g., similar to the operations ofthe user interface 211 described above with respect to FIG. 2A). Asanother example, the sensor 204-1P may be utilized for navigation andother functions of the propulsion portion 201B when it is separated fromthe storage compartment portion 202B (e.g., similar to the operations ofthe sensor 204-1 described above with respect to FIG. 2A). It will alsobe appreciated that the inclusion of both of the sensors 204-1S and204-1P may improve certain navigation and other capabilities of the AGV200B. For example, once the storage compartment portion 202B is attachedto the propulsion portion 201B, the additional height of the storagecompartment portion 202B and the corresponding height of the sensor204-1S may provide additional data (e.g., due to a different angle ofperspective, field of view, etc.) that may be useful for navigation bythe propulsion portion 201B to avoid obstacles, navigate pathways, etc.Such data that is communicated to the control system 210 (e.g., throughthe coupling portion 238) may also be useful for more accuratelymonitoring/determining the clearance requirements for certain obstacles(e.g., wherein the height of the storage compartment portion 202B has ahigher clearance requirement than the propulsion portion 201B alone).

FIG. 2C depicts a block diagram of a side view of another AGV 200C,according to an implementation. The AGV 200C of FIG. 2C is similar tothe AGV 200A of FIG. 2A, and includes a storage compartment portion 202Cand a propulsion portion 201C. One difference of the AGV 200C is thatthe sensors 204-1 and 204-2, and the user interface 211 are located onthe propulsion portion 201C rather than on the storage compartmentportion 202C. In this configuration, the propulsion portion 201C is morecapable (e.g., as compared to the propulsion portion 201A) of operatingindependently of the storage compartment portion 202C when it isdetached. More specifically, the propulsion portion 201C is able tocontinue to utilize the sensors 204-1 and 204-2 (e.g., for navigation,etc.), as well as the user interface 211 for receiving user input, evenwhen the storage compartment portion 202C is detached. In thisconfiguration, the storage compartment portion 202C is also noted tocontain less electronic components as compared to the storagecompartment portion 202A. In an alternative configuration, the sensors271-274 may also be eliminated, such that the storage compartmentportion would have no electronic components and would not require anyelectronic connections, as may be desirable for certain implementations.

In various implementations, AGVs 200 may be provided in different sizes.For example, some AGVs may have length, width and height dimensions thatare each under 3 feet, while others may have length dimensions that areunder 2.5 feet and width and height dimensions under 1.5 feet. Invarious implementations, AGVs 200 may be sized to be able to travelalong various pathways (e.g., sidewalks, etc.) without causingsignificant disruption to other vehicles, people, etc. who may also betravelling along the pathways. For example, by having width dimensionsthat are less than ½ a pathway width dimension, an AGV may be able totravel and/or stop along certain types of pathways, while othervehicles, people, etc. may be able to comfortably pass by to the side ofthe AGV while also remaining on the pathway. At such sizes, numerousAGVs may be able to congregate in a relatively small area (e.g., 10, 20,30+ AGVs may be able to congregate in a 9 foot by 18 foot parking spaceand/or a similarly sized area in an AGV facility, etc.).

In various implementations, AGVs may also be operated during certainhours when pathways are less crowded and/or utilized (e.g., at night,such as between 2 a.m. and 6 a.m., or otherwise when pathways are lesscrowded in certain delivery areas, etc.). Operating at such hours mayalso simplify the operations of transportation vehicles, which maytravel on regular roadways which may also be significantly less crowdedand for which parking locations (e.g., within available parking spaces)may be more readily available (e.g., for parking the transportationvehicles to deploy and/or meet AGVs, etc.). In various implementations,a transportation vehicle that deploys and/or meets AGVs may be parked ina delivery area so as to be relatively close to certain deliverylocations. For example, AGVs may in some instances be directed totransporting items over the last 100-500 yards of the travel paths fordeliveries, which may in some instances correspond to the distance froma transportation vehicle to a delivery location. In someimplementations, AGVs may be utilized to transport items and/orotherwise travel for longer distances (e.g., 10+ miles, etc.)

In various implementations, AGVs 200 may also be operated at relativelylow speeds. For example, certain AGVs may have travel speeds between 3mph and 6 mph. It will be appreciated that by being of relativelysmaller sizes and operating at lower speeds, the operating requirementsfor controlling such AGVs safely may be significantly less complex thanthe operating requirements for certain other types of autonomousvehicles. For example, autonomous cars for transporting human passengersmay be significantly larger and may travel significantly faster, and maytherefore have significantly more complex requirements for safeoperation than AGVs with the example operating speeds and sizes notedabove.

FIG. 3 is a block diagram of an illustrative AGV environment 300 thatenables a user 302 to order an item that will be transported by an AGV200 to a delivery location 308. As will be described in more detailbelow, once a transportation vehicle 332 reaches a location L1, an AGV200 (e.g., which may have been transported to the location L1 by thetransportation vehicle 332, or may have travelled to the location L1from a home base location at a user's residence 308, etc.) may transportthe item from the location L1 to a user specified delivery location 308(e.g., to the user's residence, etc.). As will be described in moredetail below, in various implementations multiple locations (e.g.,similar to the locations 308, L1, etc.) may be included in an AGVenvironment and may represent delivery locations, locations from whichone or more AGVs may transport one or more items, etc. In oneconfiguration, a home base location (e.g., at the user residence), thelocation L1, and/or the transportation vehicle 332 may include chargingstations and/or servicing areas for the AGV 200. In variousimplementations, the transportation vehicle 332 may be any type ofmobile machine, such as a truck, car, watercraft, aircraft, etc., andcontrol of the mobile machine may be manual (e.g., a driver) orautomated (e.g., directly or remotely controlled by an automated system,robotic, etc.).

The AGV environment 300 includes a user interface that allows a user 302to place an order for an item that will be transported by an AGV 200 toa delivery location. As will be described in more detail below withrespect to FIG. 6, an AGV 200 may also transport an item to a pickuparea that the user will travel to for retrieving the item. In theexample of FIG. 3, the user interface may be a graphical user interface,an audio only interface, a multi-mode interface, or any other interfacefor interacting with the user 302. The user interface may be provided tothe user 302 through any type of electronic device 306, such as atablet, desktop, laptop, smart phone, personal digital assistant,netbook, etc. The user interface may be delivered to the electronicdevice 306 by one or more remote computing resources 310 that make uppart or all of an electronic commerce shopping environment. In otherembodiments, the user interface may be in direct communication between auser and an agent.

The remote computing resources 310 may form a portion of anetwork-accessible computing platform implemented as a computinginfrastructure of processors, storage, software, data access, and othercomponents that is maintained and accessible via a network 309.Services, such as e-commerce shopping services, offered by the remotecomputing resources 310 do not require that the user have knowledge ofthe physical location and configuration of the system that delivers theservices. The electronic device 306 may communicatively couple to theremote computing resources 310 via the network 309 which may representwired technologies (e.g., wires, USB, fiber optic cable, etc.), wirelesstechnologies (e.g., RF, cellular, satellite, Bluetooth, etc.), and/orother connection technologies. The network 309 carries data between theelectronic device 306 and the remote computing resources 310.

After receiving from a user 302 an order for an item that may betransported by an AGV 200 to a delivery location, the electronic device306 may send this information to the remote computing resources 310 overthe network 309. As illustrated, the remote computing resources 310 mayinclude one or more servers, such as servers 320(1), 320(2), . . . ,320(N). These servers 320(1)-(N) may be arranged in any number of ways,such as server farms, stacks, and the like that are commonly used indata centers. Furthermore, the servers 320(1)-(N) may include one ormore processors 322 and memory 324 that may store a management system326.

The management system 326 may be configured, for example, to performorder planning and filling of transportation vehicles 332 and/or AGVswith orders (e.g., at a materials handling facility 330) for transportto locations (e.g., location L1) where AGVs may further transport theitems to user specified delivery locations. In fulfilling orders thatmay be transported by an AGV, the materials handling facility 330 mayfulfill orders using any of the processes discussed above with respectto FIG. 1. The transportation vehicles 332 and/or AGVs 200 maycommunicatively couple to the remote computing resources 310 via thenetwork 309. For example, the communications to and from thetransportation vehicles 332 and/or AGVs 200 may utilize wirelessantennas of the transportation vehicles and AGVs.

The management system 326 may also be configured, for example, tocommunicate with the transportation vehicles 332 and/or AGVs 200. Invarious implementations, the general activities of transportationvehicles and AGVs, including those related to the planning andimplementation of the transportation vehicles and AGVs receiving andtransporting items, may be coordinated and/or otherwise controlled bythe management system 326. For example, the management system 326 mayreceive or determine schedule data for the travel of the transportationvehicles and/or AGVs and/or may otherwise direct the distribution and/orreceiving of items by transportation vehicles and/or AGVs.

In various implementations, an AGV 200 may be configured to communicatewith other AGVs 200, the management system 326, etc. regarding varioustypes of data and/or information. For example, an AGV 200 may senseand/or receive travel related data (e.g., related to travel conditions,obstacles, etc. for travelling along a travel path). In variousimplementations, travel related data that is sensed and/or collected byan AGV may be shared with a management system, other AGVs, othervehicles, and/or other entities. The AGVs may also use this informationlocally, in combination with other received travel related data (e.g.,for navigating current travel paths, etc.). Such travel related data maybe centrally stored and/or otherwise processed to be utilized forcreating and/or updating travel maps, informing other AGVs regarding theavailability and/or conditions of certain travel paths, etc.

In various implementations, the remote computing resources 310 and/ormanagement system 326 may also receive tracking data (e.g., GPS)regarding the coordinates of the transportation vehicles and/or AGVs.The GPS data may be utilized for various purposes, such as answeringlocation status requests or for sending notifications regarding thecurrent locations of the transportation vehicles and/or AGVs. Forexample, a user may request that a notification be sent when atransportation vehicle and/or an AGV with an ordered item isapproaching. As another example, a notification may be sent to an AGVwhen a transportation vehicle is on the way to or otherwise approachinga meeting area where the AGV is to meet the transportation vehicle foracquiring an identified item from the transportation vehicle.Notifications may also be sent from the transportation vehicle 332and/or AGV 200 to the remote computing resources 310 and/or managementsystem 326 regarding various events (e.g., when an AGV has departed froma transportation vehicle with an item for transport to a deliverylocation, when an AGV has arrived at a delivery location with anacquired item, etc.). In various implementations, the remote computingresources 310 and/or management system 326 may also receive informationand/or otherwise communicate with materials handling facilities 330,delivery locations 308 at users' residences, etc. (e.g., regardingactivities related to the deliveries of ordered items, etc.).

In various implementations, the management system 326 may include and/orotherwise be formed from various distributed components and/or variousfunctions of the management system 326 may be performed in a distributedmanner. For example, various AGVs, transportation vehicles, locations,etc. may include various types of computing capabilities that may eachcommunicate and/or otherwise perform functions for managing and/orotherwise making determinations regarding the operations of the AGVs,transportation vehicles, etc. In various implementations, travel pathsand/or other travel parameters for AGVs and/or transportation vehiclesmay be determined based on input/data received from multiple sources(e.g., AGVs and/or transportation vehicles within an area and/or othersources may provide data regarding current travel conditions, travelpaths, congestion, etc.).

FIG. 4 depicts a block diagram of another AGV environment 400, accordingto some implementations. In the example of FIG. 4, transportationvehicles 332(A), 332(B) and 332(C) may be part of transportation system(e.g., a delivery system and/or a receiving system for delivering and/orreceiving items, etc.), as will be described in more detail below.Corresponding geographic areas 401(A), 401(B), 401(C) are served by eachtransportation vehicle 332(A), 332(B), 332(C), respectively. Eachgeographic area may include a number of locations (e.g., deliverylocations and/or receiving locations). In certain examples that will bedescribed below, the geographic areas 401(A), 401(B) and 401(C) maycorrespond to delivery areas and/or receiving areas, and locationsL1(A)-L3(A), L1(B)-L2(B) and L1(C)-L2(C) within each of the respectivegeographic areas may correspond to delivery locations and/or receivinglocations, depending on the specific example.

Each of the transportation vehicles 332(A)-332(C) is shown to have anumber of corresponding autonomous vehicles of different types. Asshown, the transportation vehicle 332(A) has associated AGVs 200(A1) and200(A3) and an autonomous vehicle 420(A2) (i.e., an unmanned aerialvehicle (“UAV”)). The transportation vehicle 332(B) is shown to haveassociated AGVs 200(B1), 200(B2) and 200(B3) and autonomous vehicle420(B1) (i.e., a UAV). The transportation vehicle 332(C) is shown tohave an associated AGV 200(C2) and an autonomous vehicle 420(C1) (i.e.,a UAV).

In various implementations, the AGVs 200 and other autonomous vehicles420 may be carried by, or travel with, the respective transportationvehicles 332 as the transportation vehicles travel to and from deliveryand/or receiving areas. For example, AGVs 200 may be carried in storageareas of the transportation vehicles for being deployed from thetransportation vehicles (e.g., either with ordered items already placedin the storage compartments of the AGVs, or with ordered items carriedseparately in the transportation vehicle to be placed in the AGVs beforedeparting from the transportation vehicles). Alternatively, some or allof the AGVs 200 and/or other autonomous vehicles 420 may be stationed atlocations within the respective geographic areas, and may be utilizedfor transporting items to and from the transportation vehicles 332 whenthe transportation vehicles 332 are in the respective geographic areas.In various implementations, the AGVs 200 and/or other autonomousvehicles 420 that are stationed in the geographic areas may also beutilized for other purposes (e.g., transporting items for local pickupsand deliveries). In various implementations, the AGVs 200 and/or otherautonomous vehicles 420 may receive instructions and/or be controlled orotherwise directed by the respective transportation vehicles 332 and/orthe management system 326. For example, the transportation vehicle 332and/or the management system 326 may send instructions to the AGVsand/or other autonomous vehicles to transport items from thetransportation vehicle 332 to user specified delivery locations when thetransportation vehicle 332 is within a delivery area that includes theuser specified delivery locations.

In various implementations, a delivery or receiving area may generallybe defined as any area that includes delivery or receiving locations.The areas may represent a travel range within a specified period of timefor one or more types of AGVs and/or other autonomous vehicles from astopping location or travel route of a transportation vehicle. Theexample circular shapes of the geographic areas 401(A)-401(C) mayrepresent example travel ranges of a type of AGV and/or other autonomousvehicle from a stopping location for a transportation vehicle at thecenter of the circular area. In one implementation, a single delivery orreceiving area may be represented by a combination of geographic areas.For example, the combination of geographic areas 401(A) and 401(B) mayrepresent a single delivery or receiving area for a transportationvehicle (e.g., wherein the transportation vehicles 332(A) and 332(B) mayrepresent the same transportation vehicle as it travels through thedifferent areas). In various implementations, the combined geographicareas 401(A)-401(C) may represent a single delivery and/or receivingarea that is serviced by the multiple transportation vehicles332(A)-332(C).

In operation, when an order for one or more items is placed by a user, ashipment set may be assigned to a materials handling facility 330 forfulfillment and delivery. An order planning system (e.g., as part of, orworking in conjunction with, the management system 326) may determine ifthere is a transportation vehicle, such as transportation vehicle332(A), that will be within a geographic area 401(A) which includes adelivery location L1(A) where the user may wish to have the itemsdelivered on the desired date during a desired timeframe.

If an identified transportation vehicle will be available, themanagement system 326 may determine if it is currently indicated thatthere will be available capacity for the user's order in thetransportation vehicle prior to designating the transportation vehiclefor transporting the order. For items that have been ordered with atransportation vehicle 332(A) designated for transporting the order, theordered items may be picked and placed into one or more AGVs 200 and/orother autonomous vehicles that will be carried by the transportationvehicle and/or into one or more storage areas (e.g., bins) of thetransportation vehicle 332(A) while the transportation vehicle 332(A) isat the materials handling facility. Other items associated with otherorders may also be picked and placed in the AGVs, other autonomousvehicles and/or storage areas of the transportation vehicle 332(A) whilethe transportation vehicle 332(A) is located at the materials handlingfacility, after which the transportation vehicle 332(A) may beinstructed to travel to the designated geographic area 401(A).

In various implementations, in addition to previously designated userorders, transportation vehicles may also be used to deliver high-volumeand/or release day items. A high-volume item may be, for example, anitem that is frequently ordered, such as a popular book, shoe, videogame, tablet, etc. A release day item may be an item that will becomeavailable on the day it is released to the public (e.g., book, movie,game, toy, etc.). For high-volume and/or release day items, they may bepicked and placed in AGVs, autonomous vehicles, and/or storage areas(e.g., bins) of various transportation vehicles before thetransportation vehicles travel to designated delivery areas so that theitems will be immediately available to be delivered by AGVs and/or otherautonomous vehicles on the release day. In various implementations,certain storage areas of a transportation vehicle may be reserved forhigh-volume and/or release day items and/or any available storage areasthat have not been filled with user orders may be utilized for thehigh-volume and/or release day items. For example, when a transportationvehicle is ready to travel to a delivery area, any of the empty storageareas may be filled with high-volume and/or release day items in casethose items are ordered by users. When a user orders one of thehigh-volume and/or release day items, a storage area containing one ofthose items may be associated with the user's order and the item madeimmediately available for delivery by an AGV and/or other autonomousvehicle.

As illustrated in FIG. 4, in one example the transportation vehicle332(A) is shown to initially travel from the materials handling facility330 on a route that goes through the geographic area 401(A) (e.g., whichin this instance may be designated as a delivery area). In variousimplementations, the transportation vehicle 332(A) may have a singlecentral stopping location within the geographic area 401(A), which AGVsand/or other autonomous vehicles may depart from and/or return to,before the transportation vehicle 332(A) continues to travel.Alternatively, the transportation vehicle 332(A) may have multiplestopping locations and/or may continue to move along the route throughthe geographic area 401(A) while the AGVs and/or other autonomousvehicles depart from and return to the transportation vehicle 332(A) atdifferent locations along the route.

In various implementations, when an item is to be delivered, a selectionmay be made between the different types of AGVs and/or other autonomousvehicles for transporting the item. For example, when a delivery is tobe made, an AGV and/or other autonomous vehicles may be selected for thedelivery based on certain transportation factors. In one implementation,one type of AGV and/or other autonomous vehicle may be preferable overanother based on transportation factors such as current trafficconditions, weather, safety, travel speed, travel cost, etc. In thefollowing examples, when an AGV or other autonomous vehicle that iscarried by a transportation vehicle is selected or otherwise designatedfor a delivery of an item, the AGV or other autonomous vehicle maydeploy from the transportation vehicle and travel along a travel path todeliver the item to the respective delivery location. In variousimplementations, such operations may be performed as part of adistributed system and/or may be instructed, coordinated, monitored,etc. by the management system 326 and/or control systems of the AGVs,transportation vehicles, locations, remote computing resources, etc. Asnoted above, some or all of the AGVs and/or other autonomous vehiclesmay be stationed at and/or otherwise travel to locations within therespective geographic areas, and may be utilized for transporting itemsto and from the transportation vehicles and/or other locations.

As another illustrative example, the AGV 200(A1) is shown to deliver anitem from the transportation vehicle 332(A) to a delivery locationL1(A). As indicated by the dotted lined travel path, the AGV 200(A1) maythen travel from the delivery location L1(A) to the materials handlingfacility 330, rather than back to the transportation vehicle 332(A).This type of travel path may be followed for a number of reasons (e.g.,the transportation vehicle 332(A) may have subsequently left thegeographic area 401(A) in which case the materials handling facility 330may be closer to the current location of the AGV 200(A1), the AGV200(A1) may have an item that is to be delivered to the materialshandling facility 330, the transportation vehicle 332(A) may havealready returned to the materials handling facility 330, etc.). In analternative implementation, the travel path may indicate that the AGV200(A1) has traveled from the materials handling facility 330 to deliveran item to the delivery location L1(A), and then traveled to thetransportation vehicle 332(A). For example, the AGV 200(A1) may havedelivered an item directly from the materials handling facility 330 tothe delivery location L1(A), and then traveled to a meeting area withthe transportation vehicle 332(A) (e.g. which may be the closesttransportation vehicle) for further transport. As will be described inmore detail below with respect to FIGS. 7A and 7B, when arriving at ameeting area for meeting a transportation vehicle, an AGV may join otherAGVs that are also waiting at the meeting area for the transportationvehicle (e.g., wherein the other AGVs may also be waiting for furthertransport by the transportation vehicle after having completed adelivery and/or waiting to acquire items for delivery, etc.).

As another illustrative example, the autonomous vehicle 420(A2) (i.e., aUAV) is shown to travel to a delivery location L2(A) to deliver an itemfrom the transportation vehicle 332(A), and then travel back to thetransportation vehicle 332(A). The AGV 200(A3) is shown to travel to adelivery location L3(A) to deliver an item from the transportationvehicle 332(A), and then subsequently travel to a differenttransportation vehicle 332(B). Such a travel route may be followed by anAGV for a number of reasons (e.g., the transportation vehicle 332(A) mayhave subsequently left the area and the transportation vehicle 332(B)may be closer, the AGV 200(A2) may have an item that is to be deliveredto the transportation vehicle 332(B), etc.). In various implementations,the transportation vehicles 332(A) and 332(B) may be representative ofthe same transportation vehicle as it travels from the geographic area401(A) to the geographic area 401(B), in which case the AGV 200(A3) maybe described as returning to the transportation vehicle that itoriginated from after the transportation vehicle has moved to adifferent location.

With respect to the transportation vehicle 332(B), the AGV 200(B1) andanother autonomous vehicle 420(B1) (e.g., a UAV) are shown to follow atleast part of a travel path together to deliver an item from thetransportation vehicle to the delivery location L1(B), and then returnto the transportation vehicle 332(B). In various implementations, one ofthe AGV 200(B1) or the autonomous vehicle 420(B1) may provide assistanceto the other for delivering the item to the delivery location L1(B)(e.g., as instructed by the management system 326, control system of thetransportation vehicle, and/or as determined through coordinationbetween the vehicles, etc.). For example, the AGV 200(B1) may requireassistance to navigate past an obstacle (e.g., a barrier, etc.), forwhich the autonomous vehicle 420(B1) may engage the AGV 200(B1) andtemporarily fly or lift the AGV 200(B1) or otherwise assist innavigating over or otherwise past the obstacle. As another example, itmay be undesirable for the autonomous vehicle 420(B1) to navigate (e.g.,fly) along the final portion of the travel path to the delivery location(e.g., due to undesirable noise levels, safety issues in proximity tothe delivery location, etc.) for which it may be preferred to have theAGV 200(B1) carry or otherwise assist the autonomous vehicle 420(B1)and/or the item to be delivered in reaching the delivery location. Invarious implementations, the AGV 200(B1) may alternatively be based atthe location L1(B) (i.e., rather than carried on the transportationvehicle 332(B)), for which as the autonomous vehicle 420(B1) fliestoward the delivery location L1(B) from the transportation vehicle332(B), the AGV 200(B1) may travel out to meet the autonomous vehicle420(B1) at a safer/quieter landing distance from the delivery locationL1(B) (e.g., at a user's residence, etc.). The AGV 200(B1) may thencarry the autonomous vehicle 420(B1) and/or the item for delivery backto the delivery location L1(B), and after the item is retrieved by auser or otherwise delivered, the AGV 200(B1) may carry the autonomousvehicle back out to a safer/quieter distance from the location L1(B) fortaking off and flying back to the transportation vehicle 332(B),materials handling facility 330, or other location.

With respect to the other AGVs from the transportation vehicle 332(B),the AGV 200(B2) is shown to deliver an item from the transportationvehicle 332(B) to the delivery location L2(B), and then return to thetransportation vehicle 332(B). The AGV 200(B3) is shown to traveldirectly from the transportation vehicle 332(B) to a transportationvehicle 332(C). In various implementations, an AGV may travel betweentransportation vehicles for various reasons (e.g., to deliver or receiveitems or supplies from one transportation vehicle to another, to betransported by a different transportation vehicle back to a materialshandling facility or other destination, to return to a transportationvehicle that the AGV was originally assigned to, as followinginstructions after delivering an item to return to whichevertransportation vehicle is closest, etc.). In various implementations,AGVs may generally receive resources from transportation vehicles (e.g.,electricity, power modules, parts, etc.) and an AGV may travel to adifferent transportation vehicle for receiving such resources if theother transportation vehicle is closer or otherwise more convenient, orif the original transportation vehicle has run out of such resources,etc.

With respect to the transportation vehicle 332(C), the autonomousvehicle 420(C1) and the AGV 200(C2) are shown to deliver items from thetransportation vehicle 332(C) to delivery locations L1(C) and L2(C),respectively, and to return to the transportation vehicle. Additionally,the AGV 200(C2) is illustrated as traveling to and from the materialshandling facility 330. In various implementations, an AGV may travelbetween a transportation vehicle and a materials handling facility for avariety of reasons (e.g., to transport items from the transportationvehicle to the materials handling facility, to receive needed items orsupplies from the materials handling facility, etc.). As anotherexample, if the transportation vehicle 332(C) is travelling to transportreceived items to the materials handling facility 330, but adetermination is made that subsequent travel of the transportationvehicle 332(C) to the materials handling facility 330 is inhibited,instructions may be sent directing one or more AGVs (e.g., AGV 200(C2))to travel to transport items to the materials handling facility 330.

In various implementations, in a geographic area with an increasing ordecreasing volume of deliveries or receiving of items, the managementsystem 326 may correspondingly increase or decrease the frequency ornumber of transportation vehicles and/or carried AGVs and otherautonomous vehicles that travel through the geographic area. Themanagement system 326 may also monitor the patterns of deliveries orreceiving of items over time and may adjust the schedules for thetransportation vehicles and/or AGVs and other autonomous vehicles tobetter meet the corresponding demand for delivering and/or receivingitems. The locations that the transportation vehicles travel to and/orstop at for sending out and/or meeting AGVs and other autonomousvehicles to make deliveries and/or receive items may also be adjusted tooptimize the network.

As noted above, a transportation vehicle may travel to a firstgeographic area, such as geographic area 401(A), before traveling to asecond geographic area, such as geographic area 401(B). In such aninstance, the transportation vehicles 332(A) and 332(B) may berepresentative of the same transportation vehicle as it travels to thedifferent respective geographic areas. In one implementation, asdescribed above, the first and second geographic areas 401(A) and 401(B)may each represent delivery areas where ordered items may be deliveredby the respective AGVs and/or other autonomous vehicles to userspecified delivery locations. In one example, the geographic areas401(A) and 401(B) may have been predetermined and/or otherwise be on aregular route for the transportation vehicle. As another example, thetransportation vehicle may have initially been instructed to travel tothe geographic area 401(A) based on one or more transportation factors(e.g., based on a number of scheduled deliveries to the locationsL1(A)-L3(A)), and then may be instructed to move to the differentgeographic area 401(B) due to a change in one or more of thetransportation factors (e.g., newly scheduled or anticipated deliveriesfor the locations L1(B) and L2(B)).

In another implementation, the first geographic area 401(A) mayrepresent a receiving area where the transportation vehicle receivesitems (e.g., from merchants, vendors, etc.), after which thetransportation vehicle may travel to the geographic area 401(B) whichrepresents a delivery area where the received items may be delivered byAGVs and/or other autonomous vehicles to user specified deliverylocations. In various implementations, a given geographic area may alsorepresent both a delivery area and a receiving area, wherein deliverylocations and receiving locations may be included within the samegeographic area. For example, the geographic area 401(A) may represent areceiving area that includes receiving locations L1(A) and L2(A), andmay also represent a delivery area that includes a delivery locationL3(A).

In various implementations, an item received at a receiving location byan AGV may be delivered directly to a user specified delivery locationby the AGV rather than back to the transportation vehicle. For example,instructions may be provided that an item received by an AGV from areceiving location L2(A) should be delivered directly to a userspecified delivery location L3(A) rather than back to the transportationvehicle 332(A). In various implementations, an AGV may receive multipleitems from different receiving locations (e.g., locations L1(A) andL2(A)) before delivering the multiple items to one or moretransportation vehicles (e.g., transportation vehicle 332(A)) ordelivery locations (e.g., location L3(A)). Similarly, an AGV may receivemultiple items from a single transportation vehicle (e.g.,transportation vehicle 332(A)) or receiving location (e.g., locationL1(A)), and then travel to deliver the items to multiple deliverylocations (e.g., locations L2(A) and L3(A)). In instances where itemsare being received from or delivered to multiple locations, it may bedesirable to utilize an AGV with multiple storage compartments (e.g.,FIG. 2B). More specifically, items that are received from or deliveredto different locations may each be stored in a separate storagecompartment (e.g., for security, etc.). In various implementations,multiple AGVs and/or transportation vehicles may be utilized fordelivering different parts or items of a single user order (e.g., oneitem from a user order may be transported by an AGV 200(A1) whileanother item from the user order may be transported by an AGV 200(A3)).

Several of the examples described above regarding deliveries to deliverylocations may alternatively be described for receiving items fromreceiving locations. For example, the AGV 200(A1) may have originated atthe transportation vehicle 332(A) and travelled to a receiving locationL1(A) for receiving an item which the AGV 200(A1) subsequentlytransported to the materials handling facility 330. Alternatively, theAGV 200(A1) may have originated at the materials handling facility 330and travelled to the receiving location L1(A) for receiving the item andsubsequently transported the received item to the transportation vehicle332(A). As a similar example, the AGV 200(A3) may have originated at thetransportation vehicle 332(A) and travelled to a receiving locationL3(A) for receiving an item and subsequently transported the receiveditem to the transportation vehicle 332(B) (which as described above maybe a different transportation vehicle or may be the same transportationvehicle 332(A) as having travelled from the geographic area 401(A) tothe geographic area 401(B)). In either case, as part of transporting theitem to the transportation vehicle 332(B), the AGV 200(A3) maysubsequently navigate into (e.g., up a ramp into the transportationvehicle 332(B)) or otherwise be engaged by the transportation vehicle332(B) for subsequently travelling with the transportation vehicle332(B).

In various implementations, a transportation vehicle may itself travelto delivery locations and/or receiving locations for delivery and/orreceiving of items. For example, in one implementation thetransportation vehicle 332(A) may travel to the receiving location L3(A)to receive items, and then may travel to the geographic area 401(B)where the items will be delivered by AGVs 200(B1) and 200(B2) todelivery locations L1(B) and L2(B). Alternatively, or in addition, thetransportation vehicle 332(A) may receive items as transported by AGVs200(A1) and 200(A3) from receiving locations L1(A) and L3(A), and thenmay travel to the delivery location L1(B) where the transportationvehicle may deliver the items. In various implementations, the materialshandling facility 330 may also be designated as a delivery and/orreceiving location that transportation vehicles and/or AGVs may travelto and from for delivering and/or receiving items.

In various implementations, the receiving locations may also representlocations for receiving an item that is to be returned by a user. Forexample, when a user wishes to return an item, the user may schedule areceiving location (e.g., at or near the user's residence or place ofwork), where the item may be received by an AGV and subsequentlytransported back to a transportation vehicle. In another implementation,a user may request that an AGV be utilized to deliver an item to a userspecified delivery location, and then wait for the user to determinewhether the user wishes to keep the item. For example, a user may have apair of shoes delivered by an AGV, and then determine that the shoes arethe wrong size or color, for which the user may wish to have the AGVsubsequently transport the shoes back to a transportation vehicle for areturn. In another implementation, a return may be expected as part of adelivery process for an item. For example, when an item is delivered,the AGV that delivered the item may be utilized for certain types ofreturns (e.g., returning a defective or worn-out item in exchange forthe new item that has been delivered, returning packaging that wasutilized for protecting the item during delivery but which is no longerneeded, etc.).

In various implementations, when a user returns an item, a credit orother compensation may be issued for the received item that may initiatea refund or replacement process, once the item is received by an AGV ora transportation vehicle. Similarly, merchants or vendors may have acredit issued or receive other compensation for an item once the item isreceived by an AGV or at the transportation vehicle. It will beappreciated that by issuing credits or other compensation for receiveditems when they are received by an AGV or transportation vehicle,refunds, payments, etc. may be initiated more quickly (e.g., as comparedto traditional systems where an item would need to be received at amaterials handling facility before a credit for the item would beissued).

In the example of FIG. 4, each of the transportation vehicles332(A)-332(C) is illustrated as being at a respective stopping location450(A)-450(C) within the delivery areas of each of the respectivegeographic areas 401(A)-401(C). In various implementations, each of therespective stopping locations 450(A)-450(C) may be a location at whichthe respective transportation vehicle may stop (e.g., be parked), andfrom which various AGVs that are carried by the transportation vehiclemay be deployed. For example, after the transportation vehicle hasstopped (e.g., parked) at a respective stopping location, the AGVs maydisembark (e.g., down a ramp to an adjacent sidewalk and/or as otherwisedeployed, etc.) from the transportation vehicle, and then may travel torespective delivery and/or receiving locations for delivering and/orreceiving items.

As will be described in more detail below with respect to FIGS. 7A-7C,the respective stopping locations 450(A)-450(C) may also be withinrespective meeting areas where other AGVs that have travelled from otherlocations (e.g., from home base locations at user residence's) may meetthe transportation vehicles. For example, the stopping location 450(A)of the transportation vehicle 332(A) may be within a meeting area thatincludes a stopping location 450(A1) that the AGV 200(A1) has travelledto and stopped at for meeting the transportation vehicle 332(A) (e.g.,for acquiring an item that is to be delivered to the location L1(A)). Invarious implementations, the stopping location 450(A1) may be adjacentto the stopping location 450(A). For example, the stopping location450(A1) may be on a sidewalk that is adjacent to the stopping location450, which may be in a parking location (e.g., in an available parkingspace) for the transportation vehicle 332(A). In variousimplementations, as will be described in more detail below, multipleAGVs may travel out and congregate in a meeting area for meeting with atransportation vehicle. As part of this process, the AGVs may stop inrespective AGV stopping locations within the meeting area, which may beadjacent to each other (e.g., on a sidewalk), as well as being adjacentto a transportation vehicle stopping location (e.g., a parking locationon the street) that is also within the meeting area. In some instances,the AGVs may travel to the respective AGV stopping locations in themeeting area before the transportation vehicle arrives, and in someinstances one or more of the AGV stopping locations may be within orotherwise the same as the transportation vehicle stopping location. Forexample, the AGVs may move into the stopping/parking location (e.g., inthe parking space) that will be for the transportation vehicle once itarrives so as to save the stopping location for the transportationvehicle and/or to allow the AGVs to congregate in a meeting area thatoccupies a parking space rather than taking up space on a sidewalk, etc.Once the transportation vehicle arrives, the AGVs may move (e.g., withinthe parking space, or to another adjacent parking space, or up on asidewalk, or to other area, etc.) so as to make room for thetransportation vehicle to park.

In various implementations, an AGV environment may include multiplematerials handling facilities, associated transportation vehicles and/orAGVs (e.g., similar to the materials handling facility 330,transportation vehicles 450 and/or AGVs 200 of the AGV environment 400,etc.) In such configurations with multiple materials handlingfacilities, the geographic areas (e.g., areas 401) serviced by thedifferent materials handling facilities and/or vehicles may overlapand/or the vehicles (e.g., transportation vehicles, AGVs, etc.) maytravel between the different materials handling facilities, geographicareas, etc. In various implementations, one or more of the locations ofthe AGV environment 400 as illustrated in FIG. 4, or other locations,may be representative of locations of other materials handlingfacilities, etc. For example, in one implementation, one or more of thelocations L1(A), L2(B) and/or L2(C), etc. may be representative oflocations of one or more additional materials handling facilities 330,wherein the AGVs 200 and/or the transportation vehicles 332 may travelbetween the different materials handling facilities and/or to or fromthe various locations to perform functions such as those described above(e.g., for transporting items, etc.).

In various implementations, the transportation vehicles and/or AGVs mayalso have capabilities for on-demand production of items. For example,books may be produced through an on-demand printing process utilizing aprinter within a transportation vehicle or AGV. As another example, athree-dimensional printer may be utilized within a transportationvehicle or AGV for producing items. As another example, an oven within atransportation vehicle or AGV may be utilized to cook an item (e.g., apizza) that is carried within the transportation vehicle or AGV in anuncooked state (e.g., as stored in a refrigerated storage compartment,etc.) or is otherwise acquired along a travel path of the transportationvehicle or AGV.

Such items may be produced on-demand to fulfill user orders that may beplaced at various times (e.g., after the transportation vehicle and/orAGV has left a materials handling facility, while the transportationvehicle and/or AGV is travelling along a travel path or is at a stoppinglocation, etc.). With respect to items that are produced on-demand by atransportation vehicle, in various implementations the items may besubsequently transported from the transportation vehicle (e.g., to adelivery location, etc.) by an AGV, etc. In various implementations,on-demand production capabilities of an AGV may be provided by a deviceand/or machine (e.g., printer, oven, etc.) that is included as part ofan AGV storage compartment portion and/or may be sized and configured tofit and operate within an AGV storage compartment portion. In variousimplementations, an on-demand production device and/or machine may beinserted inside an AGV storage compartment portion at a materialshandling facility, or may be carried inside a transportation vehicle tobe inserted inside an AGV storage compartment portion, after which anon-demand item may be produced within the AGV (e.g., while travelling)for delivery to a delivery location, etc.

In various implementations, different types of AGVs 200 may be utilizedwithin the AGV environment 400. For example, while some AGVs mayprimarily be utilized for transporting items, other AGVs may operateand/or may otherwise be utilized to provide services and/or support toother AGVs and/or transportation vehicles. For example, an AGV 200 maybe configured to provide charging capabilities (e.g., including a largepower module and/or other power source that may be utilized for chargingother AGVs that couple to the AGV through a coupling portion, etc.). Asanother example, an AGV may provide supplies to other AGVs (e.g.,carrying replacement power modules, items, etc.). As another example, anAGV may primarily travel through a geographic area (e.g., a deliveryarea, etc.) gathering data (e.g., searching for availablestopping/parking locations for transportation vehicles and/or AGVsand/or otherwise gathering data regarding travel conditions, travelpaths, congestion, etc.). In various implementations, AGVs may alsoperform such data gathering functions as part of other routineoperations (e.g., while travelling to and/or from delivery locations,etc.). In addition to sending notifications regarding data, AGVs mayalso send notifications for other purposes. For example, an AGV thatneeds to receive maintenance may send a notification regarding themaintenance and/or requesting that a replacement AGV be sent to replacethe AGV.

FIG. 5 depicts a block diagram of another AGV environment 500, accordingto some implementations. In the example of FIG. 5, the environment 500includes a materials handling facility 330, three delivery locations508-1, 508-2 and 508-3 and an AGV facility 510 in a delivery area, and acharging station 520. An AGV 200-1 travels directly between thematerials handling facility 330 and the delivery location 508-1, whilean AGV 200-2 travels directly between the AGV facility 510 and thedelivery location 508-2, and an AGV 200-3 travels between the materialshandling facility 330, the charging station 520 and the deliverylocation 508-3. As described above with respect to FIGS. 2A-2C, invarious implementations, the AGVs 200-1, 200-2 and 200-3 may includestorage compartments with locking mechanisms, control systems to controlthe locking mechanisms, propulsion portions, etc.

In various implementations, the materials handling facility 330 maycontain ordered items that are to be delivered to delivery locations byAGVs that are deployed from the materials handling facility (e.g., asdescribed in more detail above with respect to FIGS. 1, 3 and 4). Forexample, a control system 210 of the AGV 200-1 may control thepropulsion portion of the AGV (e.g., as described above with respect toFIGS. 2A-2C) to deploy the AGV 200-1 from the materials handlingfacility 330 with an ordered item contained in a storage compartment ofthe AGV, and to further navigate the AGV along a travel path from thematerials handling facility 330 to the delivery location 508-1. Once theAGV 200-1 arrives at the delivery location 508-1, the control system maycontrol the locking mechanism to unlock the storage compartment toenable the ordered item to be removed from the storage compartment(e.g., as will be described in more detail below with respect to FIG.14). In various implementations, the distance between the materialshandling facility 330 and the delivery location 508-1 may be relativelylong (e.g., 10 miles, 30 miles, or 60 miles or more), for which the AGV200-1 may utilize various techniques for long-range travel. For example,various energy conservation and/or recharging techniques (e.g., solarcharging, propellers for generating electricity from wind power,regenerating electricity from wheel motors when travelling downhill,directing travel with the wind, avoiding pathways with large hills,generally determining and following energy efficient travel paths, etc.)may be utilized. AGVs with such long range capabilities may also becapable of traveling from one materials handling facility 330 toanother, even if the materials handling facilities 330 are separated byrelatively long distances (e.g., 10 miles, 30 miles, 60+ miles, etc.).

In various implementations, various factors may be analyzed to determinewhere and when AGVs will utilize such energy conservation and/orrecharging techniques. For example, based on the current charge level ofthe power module of the AGV 200-1, the distance to be travelled to thedelivery location 508-1, the current travel conditions, etc., it may bedetermined that the AGV 200-1 will be required to perform at least onerecharging procedure along the travel path to the delivery location508-1 to recharge the power module of the AGV. In variousimplementations, the AGV 200-1 may include a solar charging mechanism,and the recharging procedure may include utilizing the solar chargingmechanism to receive sunlight to recharge the power module. As describedabove with respect to FIG. 2A, the orientation of the solar chargingmechanism may be adjustable relative to the orientation of thepropulsion portion, and the recharging procedure may include adjustingthe orientation of the solar charging mechanism toward the sunlight. Insuch configurations, the recharging procedure may also includecontrolling the propulsion portion to stop the AGV at a stoppinglocation where the solar charging mechanism will receive sunlight torecharge the power module.

In one example scenario, as part of the recharging procedure, the AGV(e.g., which may primarily travel during nocturnal hours), may travel toa stopping location that is determined (e.g., by the control system ofthe AGV, by a management system, etc.) where there is sunlight duringthe day, and where the AGV will stop and remain during the daylighthours to recharge the power module. It will be appreciated that bydetermining an optimized location and orientation for solar charging(e.g., where there is determined to be maximum sunlight exposure in anarea, orientation, etc.) and stopping at that location during daylighthours, the AGV may achieve a higher efficiency for solar charging than avehicle that continues to move while utilizing solar charging (e.g.,which may travel through less optimal locations and/or orientations forsolar charging while moving). It will also be appreciated that suchsolar charging techniques that involve remaining at a stopping locationsduring daylight hours are compatible with operating procedures for AGVsthat primarily travel during nocturnal hours (e.g., during which thereis less congestion for the travel of the AGVs and/or delivery vehicles,etc.). In various implementations, the recharging procedure may also oralternatively include utilizing a charging station (e.g., similar to thecharging station 520) that is located along a travel path to a deliverylocation, as will be described in more detail below.

In various implementations, the charging station 520 may be utilized toincrease the travel range of AGVs. For example, in some instances theAGV 200-3 may be able to approximately double its effective travel rangeby utilizing the charging station 520 between the materials handlingfacility 330 and the delivery location 508-3. In variousimplementations, a network of such charging stations 520 may be providedat determined intervals for utilization by AGVs to increase theeffective travel ranges. In various implementations, the chargingstation 520 may be of various types (e.g., utilizing inductive chargingwhere the AGV simply moves proximate to the charging station, or whichmay be coupled to by coupling portions 205S and/or 205P, etc.). Invarious implementations, the charging station 520 may also providevarious supplies and/or other services for the AGVs. For example, thecharging station 520 may provide fully charged replacement power modulesfor AGVs. In various implementations, the charging station 520 may alsorequire an access code to use (e.g., wherein the AGV may include anaccess mechanism that wirelessly transmits the access code to enable theAGV to utilize the charging station to recharge a power module, etc.).

In various implementations, the AGV facility 510 may supply items to theAGV 200-2 (and other AGVs) for transport to delivery locations (e.g.,delivery location 508-2). The AGV facility 510 may be a type ofmaterials handling facility that is smaller than the materials handlingfacility 330, and may receive limited items, supplies, etc. from thematerials handling facility 330 and/or from other sources (e.g., localvendors, etc.). Due to the smaller size of the AGV facility 510, it maybe more easily located in compressed urban areas (e.g., to be closer tothe delivery locations 508-1, 508-2 and 508-3). In one implementation,the AGV facility 510 may be the size of, or smaller than, a 9′ by 18′parking space, such that it may be temporarily located in a deliveryarea where parking locations (e.g., within parking spaces) areavailable. In various implementations, the AGV facility 510 may also bemobile. In such instances, a process for searching for a stoppinglocation (e.g., a parking location) for the AGV facility 510 may beidentical to the process described below with respect to FIG. 12 fordetermining a stopping location for a transportation vehicle.

In various implementations, the AGV facility 510 may be a home baselocation for one or more AGVs and/or may be configured to interact withand provide items to AGVs. For example, the AGV facility 510 may includean item engagement mechanism (e.g., a mechanical arm) that is capable ofplacing items in, and removing items from, a storage compartment of anAGV. As another example, the AGV facility 510 may include an AGV accessdoor that is specifically sized to match the outer dimensions of theAGV, and which can only be accessed through use of a code/signal thatthe AGV is configured to provide/transmit. As another example, the AGVfacility 510 may include one or more docking stations that may becoupled to by coupling portions of the AGVs (e.g., coupling portions205S and/or 205P). Such docking stations may include communicationand/or charging capabilities and/or separate charging stations may beprovided (e.g., inductive charging stations for charging the powermodules 212, etc.). Wireless communication capabilities may also beprovided in the AGV facility 510 for communicating with the controlsystems 210 of the AGVs.

In various implementations, the AGV facility 510 may consist of astructure that is sized to hold a specified number of AGVs (e.g., atleast 4, 9, 16, etc.). For example, the AGV facility 510 may operate asa home base location for the AGVs 200-1, 200-2 and 200-3 and/or alocation where items may be dropped-off by a transportation vehicle forlater retrieval and delivery by the AGVs. A transportation vehicle maytransport ordered items from the materials handling facility 330 (e.g.,or from another source of items, such as a local vendor, etc.) to theAGV facility 510 (e.g., during the day) where the items for delivery areplaced (e.g., either directly from the transportation vehicle or at alater time) in the storage compartments of the AGVs 200-1, 200-2 and200-3. At a specified delivery time (e.g., between 2 a.m. and 6 a.m.)the AGVs 200-1, 200-2 and 200-3 may follow travel paths from the AGVfacility 510 to the delivery locations 508-1, 508-2 and 508-3. After theitems have been delivered (e.g., as removed from the storagecompartments of the AGVs 200-1, 200-2 and 200-3 by users, itemengagement mechanisms, etc.), the AGVs 200-1, 200-2 and 200-3 may remainat the delivery locations (e.g., if stationed there), or may followtravel paths back to the AGV facility 510 or other home baselocation(s), either immediately after delivery, or at a specified traveltime (e.g., between 2 a.m. and 6 a.m.).

In various implementations, a management system (e.g., includingcentralized and/or distributed elements, such as remote computingresources, control systems of AGVs and/or transportation vehicles, cloudbased elements, etc.) may at least partially monitor, coordinate and/ordirect, etc. the transportation of items from the AGV facility 510, thematerials handling facility 330, and/or transportation vehicles, etc. Inone example scenario for the distribution of items from the AGV facility510, a management system may receive orders for items and may direct theitems to be transported (e.g., by a transportation vehicle) from thematerials handling facility 330 to the AGV facility 510. The managementsystem may then instruct the AGVs 200-1, 200-2 and 200-3 to receive theitems in respective storage compartments of the AGVs (e.g., as removedfrom the transportation vehicle and/or AGV facility and placed in thestorage compartments of the AGVs while the AGVs are inside or outsidethe AGV facility 510, etc.). In various implementations, messages may besent (e.g., to users who ordered the items) indicating when the AGVshave received the items and identifications of the items (e.g., amessage may include a picture of an item, a description of an item,etc.)

The AGVs may then be instructed to deploy from the AGV facility 510 andto follow respective travel paths to deliver the items to the respectivedelivery locations 508-1, 508-2 and 508-3. One or more of the AGVs200-1, 200-2 and 200-3 may further be instructed to follow respectivetravel paths to return to the AGV facility 510 after completing thedeliveries of the items to the respective delivery locations 508-1,508-2 and 508-3 (e.g., wherein the AGV facility 510 may be a home baselocation for one or more of the AGVs 200-1, 200-2 and 200-3), oralternatively to remain at the respective delivery locations (e.g.,wherein or more of the AGVs 200-1, 200-2 and 200-3 may be stationed atrespective home base locations at the respective delivery locations). Inan implementation where one or more of the AGVs 200-1, 200-2 and 200-3are stationed at respective home base locations at the respectivedelivery locations, the respective AGVs may have initially beeninstructed to follow respective travel paths from the respectivedelivery locations to the AGV facility 510 before the respective AGVsreceived the items at the AGV facility 510.

As noted above, the AGV facility 510 may be of a particular size (e.g.,large enough to contain all of the AGVs 200-1, 200-2 and/or 200-3 at thesame time). In various implementations, one or more of the AGVs 200-1,200-2 and/or 200-3 may be instructed or otherwise operate to utilizerespective coupling portions of the AGVs to couple to respective dockingstations inside the AGV facility (e.g., for recharging, communications,etc.). In an implementation where the AGV facility 510 is mobile and isof a size that fits within a parking space (e.g., a 9′ by 18′ parkingspace), the AGV facility to be positioned at a stopping location (e.g.,within a parking space) that is within a delivery area that includes thedelivery locations 508-1, 508-2 and 508-3, and from which the AGVs200-1, 200-2 and 200-3 will deploy to deliver the items to therespective delivery locations 508-1, 508-2 and 508-3.

As will be described in more detail below with respect to FIG. 11, aspart of the travel between the various locations, the AGVs 200-1, 200-2and 200-3 may encounter various obstacles and/or access barriers (e.g.,doors, gates, etc.) The AGVs 200-1, 200-2 and 200-3 may be enabled withnavigation capabilities for navigating around obstacles and for openingor otherwise gaining access past access barriers (e.g., to allow an AGVto bring an item and/or storage compartment into a user's residence asinstructed by the user, to enter or depart from a materials handlingfacility 330, AGV facility 510, charging station 520, etc.). Once anitem and/or storage compartment has been delivered by the AGV to adelivery location 308 (e.g., as retrieved by the user from the AGV, oras otherwise removed from the AGV by a robotic arm of the AGV ordelivery location, etc.), the AGV may be instructed to return to thematerials handling facility 330, AGV facility 510 and/or chargingstation 520 (e.g., requiring navigation back out a door or other accesspoint of the user's residence, and/or through a door or other accesspoint of the materials handling facility 330, AGV facility 510 and/orcharging station 520, etc.).

In various implementations, the AGV may include an access mechanism thatis configured to transmit a signal, or otherwise include anidentification mechanism to cause the access barrier (e.g., a door,etc.) to be opened or otherwise unlocked to allow the AGV to navigatethrough or otherwise past the access barrier at each location. In thismanner, the delivery locations 508-1, 508-2 and 508-3 may each besecure, wherein the respective AGVs 200-1, 200-2 and 200-3 (e.g., astrusted devices by the users at the respective delivery locations) mayeach have the unique access codes/signals required for entrance and/orexit, etc. Similarly, the materials handling facility 330, AGV facility510 and charging station 520 may each be secure, wherein the respectiveAGVs 200-1, 200-2 and 200-3 (e.g., as trusted devices by the variouslocations) may have the unique access codes/signals required forentrance and/or exit, etc.

In various implementations, AGVs may be utilized for different types oftransactions (e.g., as facilitated by the management system 326, etc.).For example, a location 508-1 may be a business (e.g., a corner grocerystore, a restaurant, an office supply store, etc.) to which items aredelivered directly from the materials handling facility 330 by the AGV200-1, and for which an AGV (e.g., AGV 200-1 and/or AGV 200-2) may beutilized to deliver an item from the location 508-1 to a location 508-2(e.g., which may be a user's residence, another business, etc.). Invarious implementations, a single AGV (e.g., AGV 200-1) may include twoor more storage compartments (e.g., see FIG. 2B) and may be utilized todeliver items from the materials handling facility 330 to multipledelivery locations (e.g., the delivery locations 508-1 and 508-2). Insuch a scenario, the AGV 200-1 may receive items from the materialshandling facility 330 that are placed in the first and second storagecompartments, according to the different orders. The AGV 200-1 may thendeliver the items to the delivery locations 508-1 and 508-2, wherein atthe delivery location 508-1 only the first storage compartment may beopened, and at the delivery location 508-2 only the second storagecompartment may be opened. In such a configuration where an AGV hasmultiple storage compartments for delivering multiple orders, a separateaccess code or other mechanism may be utilized for each of the storagecompartments, so that each user may only access or otherwise receive theitem(s) that are part of their order. In such a configuration, the AGV200-1 may be provided with the unique access codes/signals required forentrance to the delivery locations 508-1 and 508-2 (e.g., as a trusteddevice by the users at each of the respective delivery locations 508-1and 508-2), as well as a unique access code/signal required for entranceto the materials handling facility 330.

Similarly, the AGV 200-2 may have multiple storage compartments and maydeliver items from the AGV facility 510 to the delivery locations 508-1and 508-2 in a similar manner. In such a configuration, the AGV 200-2may be provided with the unique access codes/signals required forentrance to the delivery locations 508-1 and 508-2 (e.g., as a trusteddevice by the users at each of the respective delivery locations 508-1and 508-2), as well as a unique access code/signal required for entranceto the AGV facility 510. In various implementations, the AGV facility510 may be associated with a community (e.g., a housing communityincluding the user residences 508-1 and 508-2), along with the AGV200-2, which may operate as a trusted device and be offered as a serviceto the residents of the community.

FIG. 6 depicts a block diagram of another AGV environment 600, accordingto some implementations. In the example of FIG. 6, the AGV environment600 includes geographic regions 601(A)-601(F) that are served byrespective distributed pickup areas 602(A)-602(F), each including AGVs.In various implementations, the positions of each of the pickup areas602(A)-602(F) and the associated AGVs within each of the geographicregions may correspond to locations where the AGVs can safely stop, parkand/or congregate for an appropriate period of time. For example, atleast some of the pickup areas may be at fixed positions that aredetermined ahead of time (e.g., including a designated space that isreserved for the AGVs, etc.). As another example, at least some of thepickup areas may be determined dynamically (e.g., depending on availablespace and preferred locations when the AGV(s) arrive in the area, etc.).In various implementations, pickup areas and/or associated AGVs may alsobe relocated based on various factors. For example, if a pickup area isdetermined to no longer have sufficient space for AGVs to safelycongregate and/or otherwise perform pickup area operations (e.g., due tocrowding by people, other vehicles, etc.), a relocation process may beperformed to determine a new pickup area. In various implementations,the pickup areas 602(A)-602(F) may in some instances be associated withor near various locations that may be within the geographic regions andconvenient to users (e.g., near transit stations, shopping areas,campuses, residential neighborhoods, next to community mailboxes, nextto a sporting event, etc.).

In various implementations, the pickup areas 602(A)-602(F) may includevarying numbers of AGVs, which may change over time as the AGVs travelto and from the pickup areas. For example, the pickup area 602(A) mayinitially include AGVs 200(A1) and 200(A2) (e.g., that have travelledfrom the materials handling facility 330) in stopping locations 650(A1)and 650(A2), respectively, after which the AGV 200(A2) may travel to thepickup area 602(B), which may then include the AGV 200(A2) in a stoppinglocation 650(B3), as well as AGVs 200(B1) and 200(B2) (e.g., that havetravelled from the materials handling facility 330) in stoppinglocations 650(B1) and 650(B2), respectively. As another example, thepickup area 602(E) may initially include AGVs 200(E1) and 200(E2) (e.g.,that have travelled from the materials handling facility 330) instopping locations 650(E1) and 650(E2), respectively, after which theAGV 200(E2) may travel to the pickup area 602(F), which may then includethe AGV 200(E2) in a stopping location 650(F3), as well as AGVs 200(F1)and 200(F2) (e.g., that have travelled from the materials handlingfacility 330) in stopping locations 650(F1) and 650(F2), respectively.The pickup areas 200(C) and 200(D) are shown to include AGVs 200(C1) and200(D1), (e.g., that have travelled from the materials handling facility330), in stopping locations 650(C1) and 650(D1), respectively.

When an order for one or more items is placed by a user, a shipment setmay be assigned to a materials handling facility 330 for fulfillment anddelivery. As will be described in more detail below with respect to FIG.9, a user may select to meet and pick up the item from an AGV, such asAGV 200(A1), that will be at a pickup area 602(A) as a deliverydestination (e.g., at either a set or dynamically determined location)within a geographically convenient region 601(A), rather than having theorder delivered to their house, apartment, office or other location.This may be convenient to the user if they may not be available when theitem would otherwise be delivered, may not want others located atalternative delivery locations to know that they have ordered an item(e.g., a mother may not want a gift for their child delivered to thehouse) or may not want the item left at an unsecure location (e.g.,front porch, mailroom) if they are not present when the item isdelivered.

When a user places an order for one or more items, an order planningsystem may determine if there is an AGV, such as AGV 200(A1), that willbe available to travel within a geographic region 601(A) of where theuser may wish to have the items delivered/available on the desired dateduring a desired timeframe. In some instances, a user may designate orpreselect preferred pickup areas 602, such as pickup areas 602(A) and602(B) (e.g., either at set locations or at approximate locations forwhich the final locations are dynamically determined). For example, auser may designate one pickup area 602(A) as a preferred pickup areanear the user's home and a second pickup area 602(B) as a preferredpickup area near the user's work. A user may also designate multiplepickup areas as being acceptable for delivery in case one pickup area isnot available (e.g., no available AGVs for travelling to the pickuparea), such as designating either of pickup areas 602(A) or 602(B) asbeing acceptable delivery locations near the user's home.

For an item that has been ordered with a pickup area and associated AGV200(A1) designated for the delivery, the ordered item may be picked andplaced into a storage compartment of the AGV 200(A1) while the AGV200(A1) is at a materials handling facility 330 or at another source forthe item (e.g., from a vendor). Other items associated with other ordersmay also be picked and placed in other storage compartments of the AGV200(A1) while the AGV 200(A1) is located at the materials handlingfacility or other source of items, and then the AGV 200(A1) may begintravel toward the pickup area 602(A) within the corresponding geographicregion 601(A). In an instance where an order is to be delivered to theAGV 200(A1) after the AGV 200(A1) has already begun travel and/orreached the pickup area 602(A), the order may be picked into one or moredelivery containers, transported to the AGV 200(A1) (e.g., by atransportation vehicle, courier, etc.), and may be placed in a storagecompartment of the AGV 200(A1) and made available for retrieval by theuser.

AGVs (e.g., which may travel to pickup areas) may also be used todeliver high-volume and/or release day items. A high-volume item may be,for example, an item that is frequently ordered, such as a popular book,shoe, video game, tablet, etc. A release day item may be an item thatwill become available on the day it is released to the general public(e.g., book, movie, game, toy). For high-volume and/or release dayitems, they may be picked and placed in storage compartments of variousAGVs before the AGVs travel to pickup areas so that the items will beimmediately available to users or available for pickup on the releaseday. In various implementations, certain storage compartments of certainAGVs may be reserved for high-volume and/or release day items and/or anyavailable storage compartments (e.g., in an AGV with multiple storagecompartments, as illustrated in FIG. 2B) that have not been filled withuser orders may be utilized for the high-volume and/or release dayitems. For example, when an AGV is ready to travel to a pickup area, anyempty storage compartments may be filled with high-volume and/or releaseday items in case those items are ordered by users. When a user ordersone of the high-volume and/or release day items, a storage compartmentcontaining one of those items may be associated with the user's orderand the item made immediately available for retrieval by the user. In anAGV with first and second storage compartments and a transfer mechanism(e.g., as described above with respect to FIG. 2A), multiple high-volumeand/or release day items may be placed in the first storage compartment,and the transfer mechanism may be utilized to transfer one item at atime to the second storage compartment (e.g., each time after atransaction wherein a user orders and retrieves one of the items fromthe second storage compartment, etc.).

Each of the AGVs may travel to and remain at a pickup area in therespective geographic regions 601(A)-601(F) for a specified period oftime before leaving the pickup area (e.g., to return to a materialshandling facility 330, to travel to another pickup area, to travel to adesignated delivery location, etc.). For example, on a given date, theAGV 200(A1) may be scheduled to be at the designated pickup area 602(A)from 12:00 noon until 4:00 pm, during which an ordered item may beretrieved by a user from the AGV 200(A1). The AGV 200(A1) may thus bescheduled to travel to the pickup area 602(A) by 12:00 noon, and thenleave the pickup area 602(A) at 4:00 pm (e.g., to return to a materialshandling facility 330, to travel to another pickup area, to travel to adesignated delivery location, etc.). In various implementations, AGVsmay in some instances be transported to and/or from various pickup areasor other locations (e.g., by a transportation vehicle 332) rather thanutilizing the propulsion portion of the AGV for travel.

In one implementation, when an AGV leaves a pickup area, another AGV maytravel to take the place at the pickup area for another timeframe (e.g.,from 4:00 pm to 8:00 pm). As illustrated in FIG. 6, multiple AGVs may beat a pickup area at the same time. For a geographic region and/or pickuparea with an increasing or decreasing volume of order retrievals byusers, a management system 326 may correspondingly increase or decreasethe frequency or number of AGVs that travel to the respective pickupareas. The management system 326 may also monitor the patterns of ordersby users over time and may adjust the schedules for the AGVs so as tobetter meet the demand from users (e.g., for preferred order retrievaltimes). It will be appreciated that the ability of the AGVs to travel toand depart from the pickup areas 602(A)-602(F) supports the ability toeasily and quickly expand or remove capacity so that the demand for thatpickup area can be satisfied. For example, during the Christmas holidayseason, additional AGVs may need to travel to a pickup area to supportthe increased demand for items ordered by users.

In various implementations, an AGV may also travel to a first geographicregion before continuing travel to a second geographic region. Forexample, as noted above the AGV 200(A2) is shown to travel from thepickup area 602(A) in the geographic region 601(A) to the pickup area602(B) in the geographic region 601(B), and the AGV 200(E2) is shown totravel from the pickup area 602(E) in the geographic region 601(E) tothe pickup area 602(F) in the geographic region 601(F). With respect tothe example of the AGV 200(A2), in one implementation, the first andsecond pickup areas 602(A) and 602(B) may each represent stoppinglocations where ordered items may be retrieved by users from the AGV200(A2) during different times of day. In another implementation, thefirst pickup area 602(A) may represent a stopping location where the AGV200(A2) receives one or more items (e.g., from a vendor), after whichthe AGV 200(A2) travels to the pickup area 602(B) where the one or moreitems may be retrieved by users. For example, produce or refrigerateditems may be able to be delivered in a fresher state and/or require lesstime and/or energy for refrigeration during transport if the items arepicked up from one or more vendors in the geographic region 601(A) onthe way to the geographic region 601(B). As another example, the AGV200(A2) may also receive some items from one or more materials handlingfacilities 330 before travelling to one or more pickup areas (e.g.,pickup areas 602(A) and 602(B) in geographic regions 601(A) and 601(B))to receive additional items (e.g., from one or more vendors), afterwhich it may travel to one or more additional pickup areas (e.g., pickupareas 602(E) and 602(F) in geographic regions 601(E) and 601(F)) wherethe items may be retrieved by users.

In various implementations, the AGVs at the pickup areas may also beutilized for returns of items by users. For example, a user may place anitem that is to be returned into one of the storage compartments of theAGVs. A user may also indicate that they will not be retrieving anordered item from a storage compartment of an AGV, and that they wish toinstead have the item returned. In some instances, a refund orreplacement process may be initiated when an item is received or left inthe AGV for a return. When the AGV travels back to the materialshandling facility 330, the returned item may be removed from the storagecompartment and further processed for the return.

In the example of FIG. 6, the pickup area 602(F) is shown to include apickup area configuration 603(F) that includes a control station 604 towhich the AGVs 200(E2), 200(F1) and 200(F2) are coupled (e.g.,wirelessly and/or mechanically). The control station 604 includes a userinterface 611 and a storage compartment 639. The user interface 611 isconfigured to receive and provide information to one or more users ofthe pickup area configuration 603(F) and may include, but is not limitedto, a display 613, such as a touch-screen display, a scanner 615, akeypad 617, a biometric scanner 619, an audio transducer 621, one ormore speakers 623, one or more image capture devices 625, such as avideo camera, and any other types of input or output devices that maysupport interaction between the pickup area configuration 603(F) and oneor more users. For example, the user interface 611 may also include acredit card reader, the ability to accept money (such as cash or coins)and/or the ability to vend items (e.g., stamps, labels, envelopes,shipping packages) using a vending slot 626. Providing the ability forthe pickup area configuration 603(F) to accept credit cards and/or moneyenables the delivery of orders in AGVs and/or to the storage compartment639 of pickup area configuration 603(F) for which the items are paid forat the time of pickup (e.g. cash on delivery). Likewise enabling vendingof items, such as stamps or envelopes, supports the ability for users toutilize a pickup area configuration to ship or deliver goods, asdescribed in more detail below.

In addition to including user input and output devices, the userinterface 611 may also include the ability to collect particulates, suchas for use in detection of hazardous (e.g., explosives) or bannedsubstances (e.g. drugs). In one implementation, the user interface 611may include a particulate sensor that includes a forced air ejectioncomponent 627 and an air intake component 629. The air ejectioncomponent expels air from a left side of the display 613 while a user isinteracting with or otherwise within a predetermined range of thedisplay 613. Opposite the air ejection component 627, the air intakecomponent 629 collects the ejected air and any particulates that arecollected as the air passes over the display 613 and past the user'shand or fingers as they interact with the display 613. Collectedparticulates may be scanned or otherwise processed to determine ifpotentially hazardous or banned substances may be placed into a storagecompartment of an AGV or the control station 604 using any knownparticulate testing technique. If particulates indicating the potentialpresence of hazardous or banned substances are detected, the controlstation 604 may determine to not open a storage compartment of an AGV orthe control station 604, may alert the authorities, or take otherprotective actions (such as shutting down the pickup area configurationor performing additional tests). For example, if the air intakecomponent 629 detects hazardous vapor particulates, the control station604 may contact the appropriate authorities (e.g., police, fire, etc.).

In certain smaller implementations for a pickup area configuration603(F), the user interface 611 may include more limited features. Forexample, in one implementation the user interface 611 may include arelatively small display 613 with only a keypad 617 for providing input.In certain other implementations, these and other features may also beeliminated, wherein control of the pickup area configuration 603(F) mayprimarily be provided remotely. For example, in order to access astorage compartment of an AGV or the control station 604, a user maysend or reply to a text message to or from a centralized remotelylocated control system (e.g., a management system), which controls thepickup area configuration 603(F) to open the storage compartment of theAGV or control station 604 so that the user can retrieve the ordereditem.

The control station 604 may include one or more coupling portionsconfigured to provide wired and/or wireless network connectivity withthe AGVs, as well as to remote computing resources 310, a managementsystem 326, etc. In various implementations, one or more of the AGVs maybe instructed to utilize a coupling portion to couple to the controlstation 604 after arriving in the pickup area 602(F). In variousimplementations the control station may include coupling portionssimilar to and/or compatible with the coupling portions 205S and/or 205Pof the AGVs described above with respect to FIGS. 2A-2C. In oneconfiguration, the control station and AGVs may have such couplingportions 205S and/or 205P on multiple sides, such that the AGV 200(F2)may be coupled through such coupling portions to the control station604, while the AGV(F1) may be coupled through such coupling portions tothe AGV 200(F2), and the AGV 200(E2) may be coupled through suchcoupling portions to the AGV 200(F1). In various implementations, thecoupling portions (e.g., coupling portions 205S and/or 205P) of thecontrol station 604 may provide power and/or communications with thecoupled AGVs. In such a configuration, when one AGV departs from thepickup area 602(F) (e.g., to return to the materials handling facility330), the remaining AGVs may come together to recouple to one another ina similar fashion. In an alternative implementation, rather thanphysically coupling to each of the AGVs, the control station 604 maywirelessly couple to and/or otherwise communicate with each of the AGVs.Wireless connectivity may be implemented using wireless antennas (notshown), which may provide both receive and transmit functionality. Powerand/or network communication with remote computing resources and/ordevices may be obtained from a main access point of the control station604.

The storage compartment 639 of the control station 604 may be of anysize or configuration, and in various implementations multiple suchstorage compartments may be included as part of the control station 604.Similar to the storage compartments of the AGVs (e.g., as describedabove with respect to FIGS. 2A-2C), the storage compartment 639 mayinclude an automated locking mechanism, image capture device, a motionor presence detection mechanism, temperature sensor, etc. Alternatively,in some implementations the storage compartment 639 may be utilized asan additional user interface. For example, the storage compartment 639may be removed and the space remaining may be utilized to provide ascale or other type of weight determination component to allow users toweigh items for shipment, determine the cost necessary to ship the item,and pay for shipping using the user interface 611. In variousimplementations, multiple storage compartments may be included as partof the control station 604 and/or additional storage compartment modulesthat couple to the control station, etc.

In addition to including storage compartments, power and connectivitycoupling portions, as described above with respect to FIGS. 2A-2C, eachof the AGVs may also include one or more wireless antennas (not shown)and one or more AGV control systems (e.g., FIG. 16), and/or a simplercomputing system such as a printed circuit board, RFID tag, or anythingelse that may be detectable by the control station 604 and used toidentify the AGV. The computing component(s) of each AGV may include aunique identifier of the AGV and configuration information of thestorage compartment(s) of the AGVs, which includes dimension informationand location information of each storage compartment of each AGV. TheAGV control systems may also be configured to control the actuators thatenable locking and unlocking of the storage compartments of the AGVs inresponse to receiving commands or instructions from the control station604.

In various implementations, a coupled AGV may act as a slave componentfor the control station 604, receiving instructions (e.g., open storagecompartment, close storage compartment, activate image capture device,monitor motion sensor) from a command component of the control station604 and providing responses (e.g., closed-door, open-door,object/movement detected) to the control station 604. In variousimplementations, a locking mechanism (e.g., locking mechanism 277 ofFIGS. 2A-2C) of each of the AGVs at the pickup area may be controlled bythe control station 604, either through wired or wireless communication,to effect locking and unlocking of the associated door (e.g., door 275)of the storage compartment of the AGV. For example, when a userinteracts with the control station 604 via the display 613 and providesan access code or other identifier, the control station 604 may identifya specific storage compartment 257 of an AGV associated with the accesscode or other identifier and the command component may wirelessly sendinstructions to the AGV to unlock a corresponding storage compartmentdoor 275. The instructions may include a command (e.g., unlock), anaddress or identifier of the specific storage compartment 257 and anyother information necessary for communication between the controlstation 604 and the AGV. In response to receiving the instructions fromthe command component, the control system of the AGV may activate alocking mechanism (e.g., that moves the pins of the locking mechanism277 on the door 275) of the identified storage compartment 257 of theidentified AGV such that the pins retract, thereby disengaging the lockof the storage compartment 257 allowing the door 275 to open. In someimplementations, the storage compartment 257 may also include a springmechanism (not shown) such that when the locking mechanism 277 of thestorage compartment 257 is disengaged, the spring mechanism propels thedoor 275 upward, thereby identifying to a user that the door 275 isunlocked and the storage compartment 257 is accessible.

As will be described in more detail below with respect to FIG. 12, thestopping locations 650 within each of the geographic areas 601 may bedetermined by a process which evaluates various possible stoppinglocations based on certain criteria. In various implementations, thedeterminations of the stopping locations 650 may determine where thepickup areas 602 will be (e.g., as including the stopping locations), orthe pickup areas 602 may be predetermined in which case the stoppinglocations may be determined within the predetermined pickup areas. Inthe example of FIG. 6, the pickup areas 602(A), 602(B), 602(E) and602(F) are also each meeting areas (e.g., for a meeting of at least twovehicles, in these instances at least two AGVs). As will be described inmore detail below with respect to FIG. 13, the positioning of AGVswithin a meeting area may also be determined by a process. As oneexample scenario for a repositioning of an AGV, the AGV 200(F1) maydepart from the pickup area/meeting area 602(F) (e.g., to return to thematerials handling facility 330 after an item is retrieved from astorage compartment of the AGV 200(F1)). After the AGV 200(F1) departsfrom the stopping location 650(F1), the AGV 200(E2) may move forrepositioning (e.g., may move to the stopping location 650(F1) so as totake the place of the AGV 200(F1) after it has departed). As anotherexample scenario for repositioning, it may be determined for variousreasons that the AGVs 200(F1) and 200(E2) should swap positions (e.g.,to move the AGV 200(F1) into the stopping location 650(F3) and the AGV200(E2) into the stopping location 650(F1)). For example, if itdetermined that the AGV 200(F1) will need to depart sooner that theother AGVs in the pickup area 602(F) (e.g., due to a scheduled pick upfrom the storage compartment of the AGV 200(F1)), it may advantageous toposition the AGV 200(F1) on the outside of the configuration at a timewhen it is convenient to do so (e.g., as opposed to a later time whenthe pickup area configuration 603(F) may be in use by one or more users,etc.).

As another example scenario, orders for first and second items may bereceived from respective first and second users, and the pickup area602(F) may be determined as the pickup area where the first and secondusers will retrieve the respective items from respective AGVs.Instructions may be provided for the first and second ordered items tobe placed in respective storage compartments of the AGVs 200(F1) and200(F2) while the AGVs 200(F1) and 200(F2) are at the materials handlingfacility 330, and for the respective locking mechanisms to lock therespective storage compartments of the AGVs 200(F1) and 200(F2) afterthe respective items have been placed in the respective storagecompartments. Instructions may further be provided for the AGVs 200(F1)and 200(F2) to utilize the respective propulsion portions to travel fromthe materials handling facility 330 to the pickup area 602(F) and toremain in the pickup area 602(F) for respective first and seconddesignated timeframes during which the respective first and second itemsmay be retrieved by the respective first and second users. In variousimplementations, the respective first and second designated timeframesmay be the same, may be different, may overlap, etc. For example, thefirst designated timeframe may correspond to a 1 day time window for thefirst user to retrieve the first item from the AGV 200(F1), while thesecond designated timeframe may correspond to a 2 day time window forthe second user to retrieve the second item from the AGV 200(F2),wherein the respective designated timeframes may or may not overlap.

In various implementations, respective notifications may be sent to thefirst and second users indicating the pickup area 602(F) andinstructions for retrieving the respective first and second items fromthe respective storage compartments of the AGVs 200(F1) and 200(F2) inthe pickup area 602(F), wherein the respective first and second usersmay be assigned respective first and second access codes to enableaccess to the respective storage compartments of the AGVs 200(F1) and200(F2). The instructions may include an action that is to be performedby the respective first and second users when the respective first andsecond users are in the pickup area 602(F) to enable the respectivefirst and second users to retrieve the respective first and seconditems. In one implementation, the action may be the input of an accesscode that is to be entered by the respective user on a user interface ofat least one of the respective AGV or the control station 604 of thepickup area 602(F). In another implementation, the action may beperformed with a mobile device (e.g., responding to text message, etc.)to enable the respective first or second user to retrieve the respectivefirst or second item.

In various implementations, the respective first and second items may beretrieved in accordance with a receipt of an input (e.g., an entry ofthe respective first or second access code on a user interface of therespective AGV or otherwise) that indicates that the respective first orsecond user has arrived in the pickup area 602(F) to retrieve therespective first or second item. In response to the receipt of arespective input, the respective locking mechanism of the respectivestorage compartment of the respective AGV 200(F1) or 200(F2) may becontrolled to unlock the respective storage compartment to enable therespective first or second item to be retrieved from the respectivestorage compartment by the respective first or second user. In variousimplementations, the AGVs 200(F1) and 200(F2) may include locatordevices (e.g., which are configured to transmit electronic signals, emitvarious sounds and/or activate lights, etc.) to assist the respectivefirst and second users with locating the respective AGVs 200(F1) and200(F2) in the pickup area 602(F).

In various implementations, when one of the AGVs 200(F1) or 200(F2)arrives in the pickup area 602(F), a determination may be made (e.g., bya management system and/or by a control system of the AGV, etc.) as towhether one or more other AGVs are already present in the meeting area602(F). In response to a determination that other AGVs are present, thecontrol system of the AGV may control the propulsion portion to navigatethe AGV to be positioned relative to the other AGV(s) in the pickup areaaccording to a designated order (e.g., as will be described in moredetail below with respect to FIGS. 7A-7C). In various implementations,an AGV coupling mechanism (e.g., of one of the AGVs) may be utilized tophysically couple the AGV 200(F2) to the AGV 200(F1) in the pickup area602(F) after the respective AGVs 200(F1) and 200(F2) each independentlytravel to the pickup area 602(F).

In various implementations, the pickup area 602(F) may include thecontrol station 604, and a coupling mechanism may be utilized to coupleone or both of the AGVs 200(F1) and 200(F2) to the control station 604.In one implementation, the control station 604 may be configured tocommunicate with the control system of the AGV 200(F1) to control thelocking mechanism to unlock the storage compartment of the AGV 200(F1)in response to an input that is received from the first user at thecontrol station 604. The control station may further be configured tocommunicate with the control system of the AGV 200(F2) to control thelocking mechanism to unlock the storage compartment of the AGV 200(F2)in response to an input that is received from the second user at thecontrol station 604. In various implementations, the input from thefirst user may include an input of the first access code on the userinterface 611 of the control station 604, and the input from the seconduser may include an input of the second access code on the userinterface 611.

Travel instructions may be provided for the AGV 200(F1) to utilize thepropulsion portion of the AGV to depart from the pickup area 602(F) inresponse to either the first item having been retrieved by the firstuser or the end of the first designated timeframe having been reached,and for the AGV 200(F2) to utilize the propulsion portion of the AGV todepart from the pickup area 602(F) in response to either the second itemhaving been retrieved by the second user or the end of the seconddesignated timeframe having been reached. In various implementations, adetermination that an item has not been retrieved from a respectivestorage compartment by a respective user within a designated timeframemay be made at least in part through utilization of various sensors inthe storage compartments to verify the presence and/or absence of items(e.g., as described in more detail above with respect to FIGS. 2A-2C).In various implementations, the AGVs may utilize the propulsion portionsof the AGVs to travel from the pickup area 602(F) to different types oflocations. For example, the AGVs may return to the materials handlingfacility 330 or may travel to a different materials handling facility.As another example, if the respective first or second items have notbeen retrieved within the respective designated timeframes, therespective AGVs 200(F1) or 200(F2) may travel to a different pickup area(e.g., where the respective users may travel to retrieve the respectiveitems), or may travel to a respective delivery location to deliver therespective first or second item to the respective first or second user(e.g., as a premium service or other service provided when a respectiveuser is unable to travel to the pickup area 602(F) within the respectivedesignated timeframe to retrieve the item, etc.).

In an implementation where the AGV 200(F1) includes a second storagecompartment, a third order may be received from a third user for a thirditem that is to be retrieved from a second storage compartment of theAGV 200(F1), wherein the third item may be placed in the second storagecompartment while the AGV 200(F1) is at the materials handling facility330. A notification may be sent to the third user indicating the pickuparea 602(F) and that the third item may retrieved from the secondstorage compartment of the AGV 200(F1) in the pickup area 602(F) withina designated timeframe (e.g., which may be the same timeframe that isprovided to the first user for retrieving the first item from the firststorage compartment of the AGV 200(F1)). The notification to the thirduser may include instructions for retrieving the third item from thesecond storage compartment of the AGV 200(F1) in the pickup area 602(F),wherein the third user is assigned a third access code to enable accessto the second storage compartment of the AGV 200(F1). When the thirduser arrives in the pickup area 602(F), an input may be received fromthe third user that indicates the third user has arrived in the pickuparea to retrieve the third item that is stored in the second storagecompartment of the AGV 200(F1). In response to the input that isreceived, the respective locking mechanism may be controlled to unlockthe second storage compartment of the AGV 200(F1) to enable the thirditem to be retrieved from the second storage compartment by the thirduser.

FIGS. 7A-7C depict block diagrams of another AGV environment 700,according to some implementations. In the example of FIG. 7A, threedelivery locations 708-1, 708-2 and 708-3 in a delivery area areillustrated (e.g., corresponding to user residences, etc.), which mayalso correspond to home base locations for three AGVs 200-1, 200-2 and200-3. In one example scenario, a transportation vehicle 332 travels(e.g., from a materials handling facility) with items to a stoppinglocation 750A in a meeting area 710A. The AGVs 200-1, 200-2 and 200-3may control respective propulsion portions to navigate along respectivetravel paths from respective home base locations (e.g., corresponding tothe respective delivery locations 708-1, 708-2 and 708-3 at therespective user residences) to respective stopping locations 750A-1,750A-2 and 750A-3 within the meeting area 710A. In the meeting area710A, the AGVs 200-1, 200-2 and 200-3 acquire respective items from thetransportation vehicle 332, and follow respective travel paths back tothe respective delivery locations 708-1, 708-2 and 708-3. As describedabove with respect to FIGS. 2A-2C, the AGVs 200-1, 200-2 and 200-3 mayinclude storage compartments with locking mechanisms, control systems tocontrol the locking mechanisms, propulsion portions, etc.

In various implementations, the stopping location 750A and/or themeeting area 710A that the transportation vehicle 332 is travelling tofor meeting the AGVs 200-1, 200-2 and 200-3 may be determined in variousways. For example, the stopping location 750A and/or meeting area 710Amay be determined according to a notification that is received from amanagement system 326 or remote computing resource that indicates themeeting area. As another example, the transportation vehicle 332 mayfollow a scheduled delivery route for which the stopping location 750Aand/or meeting area 710A may be determined according to a scheduled stopof the transportation vehicle 332 at a particular time. As anotherexample, coordination may be performed between the transportationvehicle 332, management system 326, and/or AGVs 200 to determine thestopping location 750A and/or meeting area 710A. Various processes fordetermining stopping locations and positioning of AGVs within meetingareas are also described in more detail below with respect to FIGS. 12and 13. In various implementations, once the stopping location 750Aand/or meeting area 710A is determined, the AGVs 200-1, 200-2 and 200-3may each receive messages or otherwise be instructed to receive one ormore items from the transportation vehicle 332 in the meeting area 710A,wherein the items are to be delivered by the AGVs from the stoppinglocation 750A in the meeting area 710A to the respective deliverylocations 708-1, 708-2 and 708-3 at the respective user residences.

Such messages or instructions may indicate a time when thetransportation vehicle 332 is expected to arrive at the stoppinglocation 750A and/or meeting area 710A. The AGVs 200-1, 200-2 and 200-3may begin travel toward the meeting area 710A far enough in advance soas to arrive before or at the same time as the transportation vehicle332. In various implementations, the AGVs 200-1, 200-2 and 200-3 maycongregate in specified patterns or arrangements at the meeting area710A (e.g., in the stopping locations 750A-1, 750A-2 and 750A-3). Forexample, the AGVs 200-1, 200-2 and 200-3 may line up at the meeting area710A in a particular order, which may simplify the transfer of itemsfrom the transportation vehicle 332 to the AGVs 200-1, 200-2 and 200-3.The AGVs 200-1, 200-2 and 200-3 may also include markings or otheridentifying symbols or devices (e.g., lights, sounds, etc.) forsimplifying the identification and transfer of corresponding items fromthe transportation vehicle 332 to the AGVs.

In one example scenario, the items in the transportation vehicle 332 maybe arranged in an order that corresponds to the order of the addressesof the delivery locations, such as the items for the AGVs 200-1, 200-2and 200-3 being arranged in order in first, second and third positions,and the AGVs 200-1, 200-2 and 200-3 correspondingly being positioned inthat order in the meeting area. In another example scenario, the itemsin the transportation vehicle 332 may be arranged in an order that doesnot correspond to the order of the delivery addresses, such as when anitem for the AGV 200-3 is in a first position, an item for the AGV 200-1is in a second position, and an item for the AGV 200-2 is in a thirdposition (e.g., wherein the first, second and third positions are inorder on a shelf or otherwise in order as arranged in the transportationvehicle 332). In accordance with this order of the items in thetransportation vehicle 332, the AGVs may be directed to be positioned inthe meeting area 710A in an arrangement such as that shown in FIG. 7A,wherein the AGVs are in an order of the AGV 200-3 first, the AGV 200-1second, and the AGV 200-2 third (e.g., relative to the transportationvehicle 332). As noted above, the positioning/arrangement of the AGVs inthis order may simplify the transferring of the items from thetransportation vehicle 332 to the AGVs (e.g., wherein the items may betransferred to the AGVs in the same order that the items are arranged onthe transportation vehicle 332). Such an order may be determined basedon various factors (e.g., based on priority of delivery, according to anorder in which items were received from various vendors, etc.).

In various implementations, when an AGV arrives in a meeting area, adetermination may be made (e.g., by a management system and/or by acontrol system of the AGV, etc.) as to whether one or more other AGVsare already present in the meeting area. For example, various sensors ofthe AGV may be utilized to provide sensed data indicating the presenceof one or more other AGVs. As another example, the AGV may include anetwork interface wherein a management system and/or other AGVs mayindicate the presence of other AGVs (e.g., according to GPS data,reported positions, etc.). In response to a determination that otherAGVs are present, the control system of an AGV may control thepropulsion portion to position the AGV relative to the one or more otherAGVs in the meeting area according to a determined arrangement of theAGVs (e.g., as described above). In various implementations,communication may be received through the network interface of the AGV(from a management system, other AGVs, a transportation vehicle, etc.)that indicates the determined arrangement of the AGVs. After the AGV isin the determined arrangement, the control system of the AGV may receivean instruction and/or may otherwise determine that the AGV is to berepositioned relative to the one or more other AGVs in the meeting area,and in response thereto may control the propulsion portion to repositionthe AGV.

While the AGV is positioned in the meeting area, a determination may bemade (e.g., by the control system of the AGV, by a management system,etc.) as to when an item has been placed in the storage compartment ofthe AGV (e.g., as received from the transportation vehicle, etc.). Inresponse to an item having been placed in the storage compartment, thecontrol system of the AGV may control the propulsion portion to navigatethe AGV along a travel path from the meeting area to a delivery locationto deliver the item. Once at the delivery location, the control systemof the AGV may receive an input of an access code and/or may otherwisebe instructed to unlock the storage compartment of the AGV so that theitem may be removed (e.g., by a user, by an item engagement mechanism,etc.) from the storage compartment at the delivery location.

As will be described in more detail below with respect to FIG. 11, aspart of the travel from the home base locations to the meeting area, andfrom the meeting area to the delivery locations (e.g., which may be thesame as the home base locations), the AGVs 200-1, 200-2 and 200-3 mayencounter various obstacles and/or access barriers (e.g., doors, gates,etc.) The AGVs 200-1, 200-2 and 200-3 may be enabled with navigationcapabilities for navigating around obstacles and for utilizing accessmechanisms for opening or otherwise gaining access past access barriers(e.g., to allow an AGV to bring an item and/or storage compartment intoa user's residence as instructed by the user). In variousimplementations, additional navigation may also be required when a homebase location is not the same as a delivery location. For example, ahome base location may be on the front porch of a user's residence, andonce an item is acquired, a user may want the AGV to bring the itemand/or storage compartment to a delivery location inside the user'sresidence (e.g., requiring navigation through a door or other accesspoint of the user's residence). Once the item and/or storage compartmenthas been delivered from the AGV (e.g., as retrieved by the user from theAGV, or as otherwise removed from the AGV by a robotic arm of the AGV orresidence, etc.), the AGV may be instructed to return to the home baselocation (e.g., requiring navigation back out a door or other accesspoint of the user's residence so as to return to the front porch, etc.).In various implementations, the AGV may include an access mechanism thatis configured to transmit a signal, or otherwise include anidentification mechanism to cause the access barrier (e.g., a door,etc.) to be opened or otherwise unlocked to allow the AGV to navigatethrough or otherwise past the access barrier.

In a different example scenario, rather than the AGVs 200-2 and 200-3both being utilized to deliver the ordered items to the deliverylocations 708-2 and 708-3, a single AGV (e.g., AGV 200-2) may includetwo or more storage compartments (e.g., see FIG. 2B) and may be utilizedto deliver the items. In such a scenario, the AGV 200-2 may travel tothe meeting area 710A and may receive items that are placed in the firstand second storage compartments, according to the different user orders.The AGV 200-2 may then deliver the items to the delivery locations 708-2and 708-3, wherein at the delivery location 708-2 only the first storagecompartment may be opened, and at the delivery location 708-3 only thesecond storage compartment may be opened. In such a configuration wherean AGV has multiple storage compartments for delivering multiple orders,a separate access code or other mechanism may be utilized for each ofthe storage compartments, so that each user may only access or otherwisereceive the item(s) that are part of their order.

In various implementations, AGVs may be utilized for different types oftransactions (e.g., as facilitated by the management system 326, etc.).For example, if a user at a location 708-1 wishes to advertise and sellan item to a user who is at a location 708-2, an AGV (e.g., AGV 200-1and/or AGV 200-2) may be utilized to transport the item from thelocation 708-1 to the location 708-2 (e.g., without requiring any directhuman contact or interaction). As another example, a location 708-1 maybe a business (e.g., a corner grocery store, a restaurant, an officesupply store, etc.) for which an AGV (e.g., AGV 200-1 and/or AGV 200-2)may be utilized to deliver an item from the location 708-1 to a location708-2 (e.g., which may be a user's residence, another business, etc.).

FIG. 7B illustrates an example in which the meeting area andcorresponding stopping locations have been relocated. In variousimplementations, a stopping location and/or meeting area may berelocated for various reasons. As an example, a determination may bemade that a group of AGVs that have congregated to meet a transportationvehicle may be able to move to a closer and/or more convenient meetingarea for meeting with the transportation vehicle, in which caserelocation may be implemented. As another example, a planned meetingarea may not have sufficient space and/or stopping locations for eitherthe AGVs and/or the transportation vehicle as the vehicles arrive (e.g.,a previously available parking location may have been taken, a sidewalkmay have become crowded, etc.), in which case relocation may berequired. As another example, a parking time limit may have expired in afirst stopping location, requiring relocation to a second stoppinglocation.

In the example of FIG. 7B, the AGVs 200-1 and 200-2 have initiallytravelled to the stopping locations 750A-1 and 750A-2 in the meetingarea 710A, and have since relocated to new respective stopping locations750B-1 and 750B-2 in a new meeting area 710B. In variousimplementations, such a relocation may have been performed before theAGV 200-3 and/or the transportation vehicle 332 arrived. For example,while the AGVs 200-1 and 200-2 were waiting, the stopping location forthe AGV 200-3 and/or the stopping location 750A for the transportationvehicle 332 (e.g., a parking location) may have been taken, and/or themeeting area 710B may have been determined to have been preferable(e.g., more convenient, closer, etc.) relative to the travel path of thetransportation vehicle 332 and/or AGV-200-3, for which the AGVs 200-1and 200-2 may have relocated to the stopping locations 750B-1 and 750B-2in the meeting area 710B. In the meeting area 710B, after the AGV 200-3arrives, it stops in a stopping location 750B-3, and after thetransportation vehicle 332 arrives, it stops (e.g., parks) in a stoppinglocation 750B, from which items may be provided to the AGVs 200-1, 200-2and 200-3 for delivery to the respective delivery locations 708-1, 708-2and 708-3.

FIG. 7C illustrates an example in which certain of the AGVs have beenrepositioned in the meeting area 710B. More specifically, after arrivingat the meeting area 710B and occupying the stopping locations 750B-1 and750B-2 (e.g., as illustrated in FIG. 7B), the AGVs 200-1 and 200-2 havemoved to be repositioned in the stopping locations 750B-2 and 750-B1,respectively (e.g., thus effectively swapping positions). In variousimplementations, such maneuvers may be performed for various reasons.For example, the AGV 200-2 may be receiving an item that requires moreurgent delivery than the item being received by the AGV 200-1 (e.g.,such as may have been determined while the transportation vehicle 332was in transit, etc.) for which the AGV 200-2 may be moved to a position(e.g., to the stopping location 750B-1) to receive the item from thetransportation vehicle 332 sooner. As another example, the order ofitems in the transportation vehicle 332 may have changed and/or beenmore recently determined, such as having been recently received from avendor while the transportation vehicle 332 was in transit, etc., forwhich the new arrangement of the AGVs at the meeting area 710B maycorrespond to the order of the items in the transportation vehicle 332(e.g., as described above with respect to FIG. 7A).

In various implementations, a management system (e.g., includingcentralized and/or distributed elements, such as remote computingresources, control systems of AGVs and/or transportation vehicles, cloudbased elements, etc.) may at least partially monitor, coordinate and/ordirect, etc. the transportation of items by AGVs, transportationvehicles, etc. With respect to the examples of FIGS. 7A-7C as describedabove, a management system and/or the vehicles may determine a meetingarea 710 (e.g., meeting area 710A and/or 710B) in which the AGVs 200-1,200-2 and 200-3 will meet the transportation vehicle 332. Each of theAGVs 200-1, 200-2 and 200-3 may travel (e.g., from respective home baselocations at respective user's residences 708-1, 708-2 and 708-3) torespective stopping locations (e.g., stopping locations 750A-1, 750A-2,750A-3, or stopping locations 750B-1, 750B-2, 750B-3, etc.) in anarrangement in the meeting area 710 ahead of when the transportationvehicle 332 is to arrive in the meeting area 710. The stopping locationsmay correspond to the positions of the AGVs 200-1, 200-2 and 200-3 inthe meeting area, and the positions/stopping locations of the AGVs200-1, 200-2 and 200-3 in the meeting area may be coordinated so thatthe AGVs 200-1, 200-2 and 200-3 are arranged in a designated order inthe meeting area 710. After arriving in the meeting area, an AGV mayutilize a coupling portion to couple to another AGV and/or dockingstation in the meeting area (e.g., for recharging, communications,security, etc.).

As noted above, in various implementations, the designated order of theAGVs in the meeting area may correspond to an order of deliveryaddresses of the respective delivery locations 708-1, 708-2 and 708-3,or may not correspond to an order of delivery addresses of therespective delivery locations (e.g., as instead corresponding to anorder of items as arranged in the transportation vehicle, etc.). Invarious implementations, the positions of the AGVs 708-1, 708-2 and708-3 in the meeting area 710 may be adjacent to one another, or may beseparated by various distances, etc. In various implementations, one ormore AGVs may be instructed to change positions in the meeting area 710before the transportation vehicle 332 arrives (e.g., as described abovewith respect to FIG. 7C and the positions of the AGVs 200-1 and 200-2).In various implementations, the meeting area 710 may be determined basedat least in part on a determination that a stopping location 750 (e.g.,a parking location 750A or 750B) is available for the transportationvehicle 332 in the meeting area 710 and/or that one or more stoppinglocations for the AGVs are available in the meeting area 710 (e.g., asadjacent to the parking location, etc.). In one instance, thedetermination that a parking location is available may be based at leastin part on receiving an indication from one of the AGVs 200-1, 200-2 or200-3 that the parking location is available.

After the transportation vehicle 332 arrives in the meeting area 710,each of the AGVs 200-1, 200-2 and 200-3 may be instructed to receive atleast one respective item from the transportation vehicle 332. Each ofthe AGVs 200-1, 200-2 and 200-3 may be instructed to transport therespective items from the meeting area 710 to the respective deliverylocations 708-1, 708-2 and 708-3. In various implementations, variousnotifications may be sent (e.g., after the AGVs receive the items fromthe transportation vehicles, after the items are delivered, etc.). Forexample, a notification may be sent to a user who ordered an item,indicating that the AGV has received the item from a transportationvehicle, and an expected delivery time and/or an identification of theitem (e.g., wherein the notification includes a picture of the item, ora description of the item, etc.).

FIG. 8 depicts a block diagram of another AGV environment 800, accordingto some implementations. As shown in FIG. 8, in response to a receipt ofan order for an item, an AGV 200 may be instructed to follow a travelpath to a delivery location 808 (e.g., corresponding to a user'sresidence) with the ordered item contained in a storage compartmentportion 202. As described above with respect to FIGS. 2A-2C, the AGV 200may be modular, wherein the storage compartment portion 202 (e.g.,including a door with a locking mechanism) may be separated (e.g.,decoupled) from the propulsion portion 201. In the example of FIG. 8,the AGV 200 delivers the storage compartment portion 202 to the deliverylocation 808, and then continues (e.g., as instructed) along a travelpath away from the delivery location 808 utilizing the propulsionportion 201 of the AGV 200.

In one implementation, at a location prior to the delivery location 808,the propulsion portion 201 of the AGV 200 may be directed to be coupledto the storage compartment portion 202 to enable the AGV 200 totransport the storage compartment portion 202 to the delivery location808. In various implementations, various securing configurations may beutilized with respect to the coupling (e.g., attachment/detachment,etc.) of the storage compartment portion 202 to the propulsion portion201. For example, a coupling portion (e.g., FIGS. 2A-2C) for couplingthe storage compartment portion 202 to the propulsion portion 201 mayinclude various types of securing components (e.g., utilizing magneticcomponents, latching components, etc.). As another example, the storagecompartment portion 202 may be securely coupled to the propulsionportion 201 such that an access code may be required to remove thestorage compartment portion 202 from the propulsion portion 201. Invarious implementations, the delivery location 808 may include a dockingstation and/or other facilities with coupling portions that allow thestorage compartment portion 202 to be securely coupled, docked and/orotherwise securely attached at the delivery location 808, wherein anaccess code may be required to remove the storage compartment portion202 from the docking station. In various implementations, a couplingportion of the docking station and/or propulsion portion 201 may alsoprovide electricity and/or communications to/from the storagecompartment portion 202. In various implementations, an access code mayalso or alternatively be required for unlocking and/or opening a door(e.g., a lid) of the storage compartment portion 202.

In one example scenario, a control system of the AGV 200 may control thepropulsion portion 201 (e.g., as instructed) to navigate the AGV along atravel path to the delivery location 808, wherein the item for deliveryis contained in the storage compartment portion 202 that is coupled tothe propulsion portion 201. In various implementations, the AGV 200 mayinclude an access mechanism and the AGV 200 may be instructed to utilizethe access mechanism to navigate past an access barrier to deliver thestorage compartment portion 202 to the delivery location 800. Forexample, the access barrier may be a door, gate, etc., and the accessmechanism may be utilized to wirelessly transmit a signal that causesthe access barrier to open.

In various implementations, the storage compartment portion 202 mayinclude various electronic components (e.g., sensors, a coolingmechanism that refrigerates the storage compartment portion, etc.). Invarious implementations, a coupling portion may provide electroniccoupling between the storage compartment portion 202 and a controlsystem of the AGV (e.g., to enable electronic communication betweenelectronic components of the storage compartment portion 202 and thecontrol system). For example, the various sensors, user interface, etc.of the storage compartment portion 202 may be able to communicate withthe control system of the AGV as coupled through the coupling portion.In one implementation, a sensor 204 (FIGS. 2A-2C) of the storagecompartment portion 202 (e.g., which may have a higher field of viewthan the propulsion portion 201) may be utilized by the control systemof the AGV for navigation along the travel path to the deliverylocation.

The control system of the AGV may receive an access code and/or otherinstructions once the AGV 200 arrives at the delivery location 808(e.g., as input on a user interface of the AGV, as received from aremote computing resource, etc.). In response to the receipt of theaccess code and/or other instructions, the control system may control acoupling portion to decouple the storage compartment portion 202 fromthe propulsion portion 201 to enable the storage compartment portion 202to be delivered to the delivery location 808. As described above withrespect to FIGS. 2A-2C, in various implementations, the AGV and/ordelivery location 808 may include one or more movement mechanisms (e.g.,rollers, actuators, mechanical arms, etc.) configured to move thestorage compartment portion 202 relative to the propulsion portion 201after the storage compartment portion 202 is decoupled from thepropulsion portion 201.

In various implementations, the delivery to the delivery location 808may include one or more additional procedures (e.g., the deliverylocation 808 may be inside a user's residence and the AGV may beinstructed to travel inside the user's residence to deliver the storagecompartment portion 202, etc.). Once the storage compartment portion 202has been delivered to the delivery location 808, the propulsion portion201 may depart (e.g., as instructed) from the delivery location 808without the storage compartment portion 202. In various implementations,notifications may be sent regarding the delivery of the storagecompartment portion 202 to the delivery location 808 (e.g., anotification may be sent to a user when the storage compartment portion202 has been delivered to a delivery location 808 at a user's residence,etc.). In various implementations, the propulsion portion 201 may travelto different types of locations from the delivery location 808. Forexample, the propulsion portion 201 may travel to an AGV facility (FIG.5), a materials handling facility, a home base location for the AGV, ameeting area for meeting a transportation vehicle that will furthertransport the AGV, and/or a location where another storage compartmentportion is to be coupled to the propulsion portion, etc.

In various implementations, storage compartment portions 202 may consistof various types of containers that may continue to function in certaincapacities after the storage compartment portion 202 is separated fromthe propulsion portion 201. For example, some storage compartmentportions 202 may include containers that are insulated and/or otherwisetemperature regulated for containing hot items, cold items, etc. Inconfigurations where the temperatures are electronically regulated, thestorage compartment portion 202 may include a power module and/or may beelectronically coupled at the delivery location (e.g., through a dockingstation, etc.). In various implementations, a user may be provided withdifferent options for customizing a storage compartment portion 202(e.g., which may be owned or otherwise regularly used by the user,etc.). For example, a user may be provided with options for selectingdifferent styles or configurations of storage compartment portionsand/or a user may be enabled to customize (e.g., decorate or otherwisemodify) a storage compartment portion 202.

FIG. 9 is a flow diagram illustrating an example process 900 forprocessing a user order for an item. This process, and each processdescribed herein, may be implemented by the architectures describedherein or by other architectures. The process is illustrated as acollection of blocks in a logical flow graph. Some of the blocksrepresent operations that can be implemented in hardware, software, or acombination thereof. In the context of software, the blocks representcomputer-executable instructions stored on one or more computer readablemedia that, when executed by one or more processors, perform the recitedoperations. Generally, computer-executable instructions includeroutines, programs, objects, components, data structures, and the likethat perform particular functions or implement particular abstract datatypes.

The computer readable media may include non-transitory computer readablestorage media, which may include hard drives, floppy diskettes, opticaldisks, CD-ROMs, DVDs, read-only memories (ROMs), random access memories(RAMs), EPROMs, EEPROMs, flash memory, magnetic or optical cards,solid-state memory devices, or other types of storage media suitable forstoring electronic instructions. In addition, in some implementationsthe computer readable media may include a transitory computer readablesignal (in compressed or uncompressed form). Examples of computerreadable signals, whether modulated using a carrier or not, include, butare not limited to, signals that a computer system hosting or running acomputer program can be configured to access, including signalsdownloaded through the Internet or other networks. Finally, the order inwhich the operations are described is not intended to be construed as alimitation, and any number of the described operations can be combinedin any order and/or in parallel to implement the process.

The example process 900 begins with the receipt of a purchase requestinitiated by a user, as in 902. Upon receiving a purchase request for anitem from a user, a determination is made as to the estimated deliverytimeframe for that item, as in 904. In some examples, this may includeidentifying a materials handling facility with the requested item instock and estimating the time required to fulfill the item to the user.In other implementations, the estimated delivery timeframe may be a setday from the date of the purchase request or a series of days. Forexample, a user may specify that the delivery timeframe is to be one dayfrom the date of the purchase request or between three and five daysfrom the date of the purchase request. In still other implementations,the estimated delivery timeframe may be a set day of the week upon whichthe user has requested to have items delivered. For example, a user maypreselect to have items ordered during the week delivered on Thursday ofevery week.

After the estimated delivery timeframe is determined, a determination ismade as to whether the item is able to be delivered by an AGV, as in906. In various implementations, AGVs may have transportationlimitations and/or restrictions related to size, weight, hazardousmaterials, travel areas, terrain, etc. for delivering items. Forexample, an item may need to be no larger than a specified size to beable to fit within a storage compartment of an AGV. As another example,AGVs may have restrictions regarding transportation of various types ofhazardous materials, etc., for which delivery may not be available forcertain types of items. If it is determined that the item is able to bedelivered by an AGV, a determination is made as to whether a delivery byan AGV is available, as in 908. If it is determined that a delivery byan AGV is available, the available AGV delivery options are presented tothe user, as in 910. In various implementations, different types of AGVdelivery options may be available. For example, a delivery vehicle maybe available that is able to transport an AGV with the item to adelivery area and to stop at a location from which the AGV can depart(e.g., along with other AGVs for other deliveries) and from which theAGV can transport the item to the delivery location (e.g., at the user'sresidence). As another example, an AGV may be stationed at a home baselocation (e.g., at a user's residence) and a delivery vehicle may beavailable that can transport the item to a meeting area with the AGV andtransfer the item to the AGV for the delivery to the delivery location.As another example, an AGV may be available that can transport the itemfrom a materials handling facility directly to the delivery location. Asanother example, an AGV may be available that can deliver the item froma materials handling facility to a meeting/pickup area where the userwill go to retrieve the item from the AGV.

After the AGV delivery options are presented to the user, adetermination is made as to whether a delivery by AGV is selected by theuser, as in 912. In various implementations, an interaction may bereceived from a user through a user interface that presents deliveryoptions to the user and receives a selection from the user (e.g., forselecting a delivery by AGV or other delivery option). In addition, invarious implementations a user may preselect or provide a preference fordeliveries by an AGV or other delivery options. If a delivery by AGV isselected by the user, the delivery by AGV is designated as the deliveryoption for the item, as in 914.

If it is determined that a delivery by AGV is not selected by the user,as in 912, or if delivery by AGV is not available, as in 908, or if theitem is not able to be delivered by an AGV, as in 906, another type ofdelivery option is designated (e.g., as selected by the user) for theitem, as in 916. In various implementations, other delivery options mayinclude traditional carrier deliveries, providing an item at a pickuparea where a user may retrieve the item, etc.

FIG. 10 is a flow diagram illustrating an example process 1000 forfilling a transportation vehicle and travelling to a location. Theexample process begins by directing items, AGVs and/or other autonomousvehicles to be placed/located in storage areas of the transportationvehicle, as in 1002. For example, as described above with respect toFIG. 1, for items that have been ordered with AGVs designated for thedeliveries, in one implementation a materials handling facility may pickand place the ordered items directly into storage areas (e.g., bins) ofthe transportation vehicle and/or storage compartments of AGVs (e.g.,which may be carried by the transportation vehicle). As another example,in addition or as an alternative to receiving items at a materialshandling facility, the transportation vehicle may also travel to areceiving area or location for receiving items (e.g., from a merchant,vendor, etc.) before travelling to a delivery area from which the itemsmay be further transported by the AGVs and/or other autonomous vehiclesto delivery locations, etc.

After the items, AGVs and/or other autonomous vehicles have beenplaced/located in the storage areas of the transportation vehicle, datamay be synchronized regarding the storage areas, as in 1004. In variousimplementations, at least some of the data that is synchronized may begenerated as the items are placed into the storage areas of thetransportation vehicle and/or storage compartments of AGVs or otherautonomous vehicles. For example, as described above with respect toFIG. 1, the transportation vehicle, individual storage areas (e.g.,bins), AGVs and/or storage compartments may include unique identifiers,such as a bar code, QR code, unique number, etc., to enable tracking,identification and association of items placed into the storage areasand/or storage compartments. Scanning of the identifiers for the storageareas/storage compartments and the picked items may result in the itemsbecoming associated with the storage areas/storage compartments andtracked with the transportation vehicle, AGVs and/or other autonomousvehicles. In various implementations, the associated data may besynchronized among computing systems of the transportation vehicle, theAGVs, the other autonomous vehicles, the management system, and/or othersystems.

After the data has been synchronized, the transportation vehicle isdirected to travel to a delivery area from which the AGVs and/or otherautonomous vehicles will further transport the items to deliverylocations, as in 1006. As described above with respect to FIG. 3, adelivery area may be defined which includes delivery locations whereitems are to be delivered. In an implementation where the transportationvehicle is carrying AGVs, deliveries to the delivery locations may beperformed by the AGVs that are deployed from the transportation vehicle(e.g., as directed by a management system, the transportation vehicle,the AGVs, etc.). In various implementations, one or more AGVs that aretransported by the transportation vehicle may have items for deliveryplaced in the storage compartments of the AGVs (e.g., while at amaterials handling facility, while in the transportation vehicle, afterhaving deployed from the transportation vehicle, etc.). One or more AGVsthat are deployed from the transportation vehicle may also be instructedto travel to a receiving location to acquire an item for delivery (e.g.,from a vendor, user, etc.), and then to travel from the receivinglocation to a delivery location to deliver the item. As described abovewith respect to FIGS. 7A and 7B, an AGV that is based near a deliverylocation (e.g., at user's residence) may begin travel toward a meetingarea in the delivery area ahead of time so as to arrive at the meetingarea before or at the same time as the transportation vehicle.

Once the transportation vehicle is in transit or has reached thedelivery area, logistics for the deliveries of the items are evaluated,as in 1008. In various implementations, the evaluation of the logisticsmay include evaluating various types of factors. For example, the numberof AGVs that are in the transportation vehicle and/or otherwise expectedto be available, as well as travel times, etc. may be related to thetiming/speed with which the deliveries may be made. As another example,the number of deliveries and/or factors regarding the delivery areas(e.g., how soon AGVs that have been deployed for a first round ofdeliveries will be able to return to perform a second round ofdeliveries, etc.) may be related to the expected timing, etc. In variousimplementations, logistics may also be evaluated during other portionsof the example process (e.g., before 1002 for determining the number ofAGVs to be carried in the transportation vehicle and/or otherwise madeavailable for transporting items, etc.). In various implementations,predictive inventory management or other techniques may also be utilizedto increase the likelihood that an AGV will be available for deliveringan item. For example, items that are expected to be in high demand fordelivery by AGVs (e.g., release day items, items for a sporting eventoccurring in a particular area, holiday shopping seasons, etc.) may bemoved ahead of time to a location from which AGVs will be able todeliver the items and/or additional AGVs may be sent ahead of time tolocations where high demand is expected to occur.

Once the logistics have been evaluated, notifications may be sent tousers, AGVs, other autonomous vehicles, the management system 326, etc.regarding the ordered items that are in the transportation vehicle, asin 1010. For example, a user may wish to receive a confirmation that anordered item is in the transportation vehicle. As another example, auser may wish to receive a notification when an AGV has been deployedfrom a transportation vehicle with an item that is to be delivered to adelivery location that is associated with the user. Such notificationsmay also be utilized to determine if an AGV or other autonomous vehicleshould continue travel toward a meeting area in the delivery area (e.g.,depending on whether or not the transportation vehicle is transportingan ordered item that the AGV or other autonomous vehicle is supposed toreceive). In various implementations, such notifications may furtherindicate an estimated arrival time of the transportation vehicle in thedelivery area and/or of an AGV or other autonomous vehicle at thedelivery location. For example, GPS signals may be utilized to determinethe coordinates of the transportation vehicle and/or AGV or otherautonomous vehicle. In various implementations, users may be able toview a map on a website that shows and updates the current location ofthe transportation vehicle and/or AGV or other autonomous vehicle, ormay otherwise receive notifications regarding current locations. Invarious implementations, expected delivery times may also be determinedaccording to the evaluation of the logistics, etc.

In various implementations, AGVs that have been deployed fromtransportation vehicles and/or have otherwise travelled to deliver itemsto delivery locations may receive further instructions for furthertravel. For example, an AGV may return to a transportation vehicle(e.g., which the AGV was deployed from) after delivering an item to adelivery location in a delivery area. As another example, an AGV mayreturn to a different transportation vehicle (e.g., the originaltransportation vehicle may have subsequently left the area and the othertransportation vehicle may be closer, the AGV may have an item that isto be delivered to the other transportation vehicle, etc.). As anotherexample, the AGV may have first and second items in respective first andsecond storage compartments and may be instructed to deliver the firstitem to a first delivery location in the delivery area and then todeliver the second item to a second delivery location in the deliveryarea.

FIG. 11 is a flow diagram illustrating an example process 1100 for anAGV travelling to a location. The example process begins with the AGVfollowing a travel path to a location, as in 1102. In variousimplementations, AGVs may travel to and from different types oflocations. For example, an AGV may be deployed from a stopping locationwhere a transportation vehicle has stopped (e.g., parked), and the AGVmay travel to a delivery location for delivering an item. As anotherexample, an AGV may travel from a home base location (e.g., at a user'sresidence) to a stopping location in a meeting area where the AGV willmeet a transportation vehicle for acquiring an item for delivery to adelivery location (e.g., at a user's residence, etc.). In variousimplementations, a home base location may be a location inside a user'sresidence, on a user's porch, in a user's garage, etc. where the AGV isgenerally stationed and waits for instructions (e.g., while utilizing acharging station and/or other facilities). As another example, an AGVmay travel to a stopping location in a pickup area where a user willmeet the AGV for acquiring an item from the storage compartment of theAGV. As another example, an AGV may travel to a location at a materialshandling facility, AGV facility, charging station, etc.

In various implementations, AGVs (e.g., which may in someimplementations travel at relatively slower speeds than other vehicles)may travel during certain hours when pathways and/or other resources(e.g., sidewalks, elevators, public transportation, etc.) are lesscrowded and/or utilized. For example, AGVs may travel during nocturnalhours, such as between 12 midnight and 8 a.m., or otherwise whenpathways and/or resources are less crowded or utilized in certain areas,etc. In various implementations, AGVs may travel utilizing certainsubterranean resources and/or pathways. For example, AGVs may travelalong travel paths utilizing subways, tunnels, etc. It will beappreciated that by travelling along pathways that are less utilized(e.g., at certain times or otherwise), AGVs may be able to travel moreefficiently and may be less likely to encounter congestion in certainareas, etc.

In various implementations, when a travel path is related to a deliveryof an item, the AGV may receive an item to be delivered (e.g., from atransportation vehicle, materials handling facility, AGV facility, user,etc.) at the beginning of the travel path to the delivery location. Invarious implementations, different types of techniques may be utilizedfor the AGV to receive an item. For example, an AGV, transportationvehicle, materials handling facility, AGV facility, receiving location,etc., may include an item engagement mechanism (e.g., a robotic arm,etc.) for engaging an item that is to be received by the AGV (e.g., byplacing the item in a storage compartment of the AGV, etc.). As anotherexample, a human agent, carrier, user, etc. may take the item and placeit in a storage compartment of the AGV.

In various implementations, once the item is placed in the storagecompartment, the storage compartment may be locked or otherwise securedfor the transport of the item to a delivery location. For example, thestorage compartment may include an electronic locking mechanism that maybe controlled to lock the storage compartment once it is determined thatthe item has been placed in the storage compartment. The determinationthat an item has been placed in the storage compartment may be madeaccording to various types of procedures. For example, an input may bereceived (e.g., by the AGV control system 210) from a carrier,transportation vehicle, remote computing resource, etc. that indicatesthat an item has been placed in the storage compartment that is to bedelivered to a delivery location. As another example, various sensors(e.g., sensors 271-273) may be utilized to determine that an item hasbeen placed in the storage compartment and has thus been received by theAGV. In various implementations, once the item is received, the AGV maybe instructed (e.g., by the management system, a remote computingresource, a control system 210 of the AGV, etc.) to travel to a deliverylocation (e.g., at a user's residence) to deliver the item. In variousimplementations, once the item is received, a message may also be sentto a user (e.g., from the AGV control system 210, the management system,a remote computing resource, etc.) that indicates that the AGV hasreceived the item and the message may also indicate an identification ofthe item (e.g., including a description or picture of the item taken bya sensor of the AGV, etc.).

In various implementations, travel path instructions and/or informationmay be received by the AGV (e.g., from the management system, from atransportation vehicle, from a remote computing resource, from otherAGVs, etc.). As part of the travelling along the travel path, thepropulsion portion of the AGV may be controlled (e.g., by the AGVcontrol system 210 as will be described in more detail below withrespect to FIG. 16) to navigate the AGV along the travel path to thelocation. For example, if the AGV is carried by a transportationvehicle, the propulsion portion of the AGV may be controlled to deploythe AGV from the transportation vehicle after the transportation vehiclehas stopped at a stopping location in a delivery area, and to navigatethe AGV along a travel path from the stopping location to a deliverylocation in the delivery area. As the travel path toward the location isfollowed by the AGV, a determination is made as to whether any obstaclesare encountered, as in 1104. If obstacles are encountered, the travelpath to the location may be altered to avoid the obstacles, as in 1106.For example, AGVs that follow roadways, sidewalks, etc. may encounterobstacles (e.g., construction, blocked pathways, etc.) for which adifferent route may be calculated and taken. In various implementations,AGVs may also send/receive information regarding travel paths,obstacles, etc. For example, an AGV that encounters an obstacle may senda notification including data regarding the obstacle to a managementsystem, other AGVs, etc. As part of such communications, other AGVs mayalso take different routes that are calculated based on the obstacles,such that data acquired by one AGV may be utilized in the determinationsof the travel paths for other AGVs, etc. In addition to the travel pathbeing altered to avoid any obstacles, a determination is also made as towhether any openable access barriers (e.g., openable doors, gates, etc.)are encountered, as in 1108. If openable access barriers areencountered, the access barriers are opened to allow the AGV to travelthrough the access barriers, as in 1110.

In various implementations, the AGV may include an access mechanism thatis configured to transmit a signal, or otherwise to cause an accessbarrier to be opened or otherwise unlocked to allow the AGV to travelthrough or otherwise past the access barrier. For example, the AGV mayinclude an access mechanism that is configured to transmit a remotecontrol signal to open an access barrier (e.g., a garage door) so as toallow the AGV to pass through or around the barrier to travel to alocation. As another example, an access barrier in a user's residencethat is sized specifically for the AGV may include a sensing mechanismthat senses an access mechanism of the AGV for unlocking the accessbarrier and allowing the AGV to pass through for travelling to alocation. It is noted that if an access barrier is not openable, it maybe treated as an obstacle according to the operations of blocks 1106 and1108.

In various implementations, an AGV may also utilize various types ofassistance (e.g., from a human, another AGV, another autonomousmechanism, etc.) as part of the navigation along a travel path (e.g., inorder to navigate past an obstacle or access barrier, etc.). In variousimplementations, an AGV may utilize different mechanisms for requestingassistance. For example, an AGV may request assistance by utilizing aspeaker (e.g., with a synthesized voice to request that a doorman open adoor, etc.), or a display or transmitted electronic message (e.g., witha request for assistance) in order to navigate past obstacles and/oraccess barriers, etc. As another example, a user may be queried (e.g.,by a voice controlled assistant that can control an access mechanism,etc.) as to whether an AGV that has arrived or is planned to arrive at alocation should be allowed access past an access barrier (e.g., a doorto the user's residence, etc.). In various implementations, a travelpath may be determined in part based on an availability of assistance atcertain locations. For example, if it is determined that an elevatoroperator is available to provide assistance (e.g., for pressing a buttonor otherwise electronically selecting a particular floor on behalf ofthe AGV, etc.), a travel path may be planned that includes travel by theelevator.

As obstacles and/or access barriers are passed, it is further determinedif the AGV will receive assistance from, or provide assistance to,another autonomous vehicle, as in 1112. For example, an AGV may requireassistance to navigate past an obstacle (e.g., a barrier, etc.), forwhich another autonomous vehicle (e.g., a UAV, etc.) may engage the AGVand/or item to be delivered and assist (e.g., through flying, lifting,etc.) in navigating past the obstacle to reach the delivery location. Asanother example, it may be undesirable for the another autonomousvehicle (e.g., a UAV) to navigate (e.g., fly) along a final portion of atravel path to the delivery location (e.g., due to undesirable noiselevels, safety issues in proximity to the delivery location, etc.) forwhich it may be preferred to have the AGV carry or otherwise assist theother autonomous vehicle and/or item to be delivered in reaching thedelivery location. If is determined that assistance is to be receivedfrom, or provided to, another autonomous vehicle, the AGV performs theassociated procedures to receive or provide the assistance, as in 1114.

As obstacles and/or access barriers are passed and any assistance isreceived or provided, the AGV continues to travel along the travel path,as in 1102, and if additional obstacles and/or access barriers areencountered, and/or if additional assistance is to be received/providedfrom or to another autonomous vehicle, the process is repeated, as in1104, 1108 and/or 1112. Once the AGV has passed any remaining obstaclesand access barriers and has received or provided any needed assistancefrom/to other autonomous vehicles as it continues to travel along thetravel path, the AGV arrives at the location, as in 1116. Once the AGVarrives at the location, notification(s) may be sent indicating thearrival at the location (e.g., to the management system, transportationvehicle, user, etc.), as in 1118. In various implementations, if the AGVis delivering an item (e.g., to a user's residence), a notification maybe included as part of a message that is sent to a user, etc. (e.g.,from the AGV, management system, etc.), which indicates that an item isbeing delivered and may also include information indicating anidentification of the item (e.g., a description of the item, a pictureof the item in the storage compartment as taken by an image capturesensor of the AGV, etc.).

In various implementations, the delivery of an item at a deliverylocation may be performed by following various procedures. For example,an item engagement mechanism (e.g., a robotic arm) of the AGV ordelivery location may be utilized to remove the item from the storagecompartment of the AGV and place the item at the delivery location(e.g., in a corner of the floor, on a counter, in a refrigerator, etc.).As another example, a delivery may consist of the AGV waiting at thedelivery location until a user arrives and removes the item from thestorage compartment of the AGV. In some instances, a user or otherentity may be required to perform an action to unlock or otherwise openthe storage compartment (e.g., by interacting with the user interface211 and entering an access code, or sending a signal from a smart phone,or utilizing another electronic or mechanical opening device, etc.) Inresponse to such unlocking procedures, the locking mechanism iscontrolled (e.g., by the AGV control system 210, management system,remote computing resource, etc.) to unlock the storage compartment toenable the item to be removed from the storage compartment at thedelivery location (e.g., by the user, etc.). In other instances, thelocking mechanism may be controlled to automatically unlock the storagecompartment once an AGV reaches a delivery location (e.g., according toa sensed location of the AGV, or according to a signal from atransmitting device within a user's residence or doorway, etc.).

After the item is delivered, a determination may also be made as towhether the delivery location is a home base location for the AGV, inwhich case the AGV may remain at the home base location. If the deliverylocation is not a home base location, the AGV may in some instancescontrol the propulsion portion to navigate the AGV to follow a travelpath to a home base location, or back to a transportation vehicle,materials handling facility, etc. In various implementations, a homebase location for an AGV may include a charging station or otherfacilities for the AGV (e.g., an inductive charging station that the AGVengages when the AGV is at the home base location, etc.). In variousimplementations, a home base location may be a location where an AGV isgenerally stationed and waits for instructions and/or is otherwiselocated when not performing deliveries or other activities, and to whichan AGV may return when such activities are completed.

In various implementations, a home base location for an AGV may be in oraround different areas of a user's residence or other location. Forexample, a home base location may be in a user's kitchen, hallway,garage, front porch, etc. As other examples, a home base location for anAGV that services a group of users may be in a common area such as ahallway, lobby, garage, etc. In some instances, a home base location maybe utilized as a delivery location where an item will be retrieved froma storage compartment of the AGV by a user. In other instances, thedelivery location may be in a more convenient area or location (e.g., asdelivered to a user's front door, kitchen, etc.), after which the AGVmay return to a home base location. In various implementations, the AGVmay return to a different home base location than the AGV started at formaking a current delivery. For example, a residence or other area mayinclude multiple home base locations, where an AGV may return towhichever home base location is most convenient or optimal for futureexpected deliveries, etc.

In various implementations, a home base location may also be a meetingarea that a transportation vehicle may travel to where items are to bereceived by AGVs. For example, an apartment building may have a homebase location in a garage, wherein one or more AGVs may be stationed atthe home base location to wait for a transportation vehicle that willenter the garage for transferring items to the AGVs. In such instances,an AGV may not need to travel to the meeting area since the home baselocation where the AGV is stationed is at a stopping location for theAGV that is in the meeting area (e.g., adjacent to a stopping locationfor the transportation vehicle that will supply the item to bedelivered, etc.). Once the items are received, the AGVs may followtravel paths (e.g., utilizing an elevator of the building) to travel tothe designated delivery locations (e.g., at users' front doors on thevarious floors of the building, etc.).

In various implementations, certain portions of the example process 1100may be repeated, in particular with regard to deliveries of multipleitems. For example, if an AGV is carrying multiple items that are to bedelivered to different delivery locations (e.g., as stored in separatestorage compartments of the AGV), the AGV may travel from one deliverylocation to another before returning to a home base location or otherdesignated location. As another example, an AGV may receive multipleitems from different transportation vehicles or other sources (e.g.,stored in separate storage compartments of the AGV), before deliveringthe multiple items to one or more delivery locations. In a configurationwhere separate storage compartments (e.g., see FIG. 3B) are utilized forseparate deliveries, a separate access code or other mechanism may beutilized for opening each of the storage compartments, so that each usermay only access or otherwise receive the item(s) that are part of theirdelivery.

In various implementations, in addition to delivering items to users,AGVs may also be utilized for delivering items to transportationvehicles as part of return processes for items. For example, when userwishes to return an ordered item, the user may place the item in an AGVwhich may travel to a delivery location which may correspond to astopping location for a transportation vehicle in a meeting area wherethe AGV will deliver the item to the transportation vehicle which willthen transport the item back to a materials handling facility or otherlocation as part of a return process for the item. In such instances,after an item that is to be returned is received in a storagecompartment of the AGV (e.g., at a user's residence, etc.), the AGV mayfollow a travel path to a delivery location/meeting area (e.g., whereother AGVs that are returning or receiving items may congregate) formeeting a transportation vehicle to which the AGV will deliver the itemfor the return. After the item has been delivered to the transportationvehicle, the AGV may in some instances then follow a travel path back toa home base location or other location, or may board or otherwise beplaced on the transportation vehicle for further transport (e.g., backto a materials handling facility where the item may be removed from thestorage compartment of the AGV if it was not already removed when theAGV met the transportation vehicle, etc.).

In various implementations, a receiving location may be designated as alocation where an AGV receives an item that is to be transported by theAGV. In the above scenario where an item is received by the AGV as partof a return process for the item (e.g., wherein the AGV is to transportthe item to a transportation vehicle for the return), the receivinglocation may in some instances be a home base location that the AGV isstationed at. For example, when a user wishes to return an item, theuser may take the item to the home base location where the AGV isstationed and may place the item in the storage compartment of the AGV,in which case the home base location is a receiving location for theAGV. Alternatively, in a scenario where an AGV is delivering an item toa user, the receiving location may be in a meeting area that the AGVtravels to or is otherwise at for receiving the item from atransportation vehicle.

FIG. 12 is a flow diagram illustrating an example process 1200 fordetermining a stopping location for a transportation vehicle and/orAGVs, according to some implementations. The example process begins witha search for available stopping location(s) (e.g., a place where thetransportation vehicle may park or otherwise stop to deploy or meetAGVs, a place where AGVs may stop to meet a transportation vehicle,etc.). In various implementations, the search for stopping locations maybe conducted by various entities. For example, the transportationvehicle may search for stopping locations once it has arrived and istravelling through the delivery area. As another example, the AGVsand/or other autonomous vehicles may search for stopping locations(e.g., before or after a transportation vehicle has arrived in thedelivery area, etc.). As another example, the management system 326 mayassist with the search for stopping locations (e.g., utilizing satelliteimagery, data provided from local street cameras, etc.). In variousimplementations, the search by each of the entities may includesearching for stopping locations for both the transportation vehicle andAGVs (e.g., if the AGVs will be meeting a transportation vehicle, thenstopping locations may be required within the meeting area for both thetransportation vehicle and the AGVs, etc.).

For conducting the search, various techniques may be utilized. Forexample, a transportation vehicle and/or AGV or other autonomous vehiclemay be instructed to travel to a preferred location (e.g., an optimallocation) that has been determined (e.g., at a center or centroid of thedelivery area, or according to an average of the coordinates of thedelivery locations, etc.) and to begin a search for available stoppinglocations that are as close as possible to the preferred location. Invarious implementations, the search instructions may include following aparticular pattern (e.g., a spiral pattern outward, etc.), which maydepend in part on the timing for finding the stopping locations. Forexample, a transportation vehicle may be instructed to stop/park by aparticular time (e.g., so as to provide certain AGVs and/or otherautonomous vehicles sufficient time to travel from a stopping locationto designated delivery locations to meet certain delivery deadlines,etc.). If a transportation vehicle is to be parked by a particular time(e.g., by 3:00 p.m.) but has arrived in a delivery area early (e.g., 30minutes early), the search instructions may include circling the areanear the preferred location for a period of time (e.g., in case astopping location becomes available) before beginning a more aggressivesearch pattern to look for stopping locations that may be further awayfrom the preferred location. As another example, a transportationvehicle may alternatively be directed to park or otherwise stop in afirst available stopping location within a delivery area (e.g., if thereis only limited time remaining for finding a stopping location, etc.).

In various implementations, as noted above other data may also bereceived and utilized for assisting with the search for stoppinglocations (e.g., images and/or data from satellites, street cameras,AGVs or other vehicles travelling in the area, users, etc.). Other datamay also be received or accessed regarding stopping locations in a givenarea (e.g., map and/or other data regarding public, private, and/orreserved stopping locations indicating coordinates, fees, parking timelimits, sizes, restrictions, statistics regarding how often the variousstopping locations are available and at what times of day, etc.). Invarious implementations, once an available stopping locations is found,data regarding the stopping location and/or the search for the stoppinglocation, etc. may be recorded (e.g., by the transportation vehicleand/or the management system) and may be stored as part of a database orother collection of data regarding the given area, etc. Such data (e.g.,regarding stopping locations, statistical availability of stoppinglocations, travel in the given area, etc.) may be collected frommultiple transportation vehicles, AGVs, other autonomous vehicles and/orother sources, and may be accessed and/or otherwise utilized to assistwith future searches (e.g., by transportation vehicles, AGVs, etc.) forstopping locations in the given area, etc.

Once one or more available stopping locations are found, a determinationis made if the stopping locations meet certain criteria, as in 1204. Invarious implementations, the criteria may be based at least in part onfactors such as the size of the transportation vehicle and/or AGVs, therequired orientations of the transportation vehicle and/or AGVs whilestopped, an amount of time that the transportation vehicle and/or AGVswill be required to stop for, etc. For example, if a transportationvehicle will be stopping (e.g., parking) at a stopping location fromwhich AGVs will be deployed, the stopping location may requiresufficient room for the transportation vehicle to park and to be in anorientation from which the AGVs can be safely deployed (e.g., out of aback or side of the transportation vehicle, etc.), and may requireenough room adjacent to the stopping location for the AGVs as they aredeployed (e.g., on a sidewalk that is not currently crowded, etc.).Similarly, if AGVs will be meeting (e.g., and waiting for) thetransportation vehicle, the AGVs may require stopping locations (e.g.,on a sidewalk, etc.) that are proximate to the stopping location for thetransportation vehicle, and where the AGVs can safely wait for and/orinteract with the transportation vehicle (e.g., to receive items fromthe transportation vehicle once it arrives, etc.). As another example,if a user is to meet an AGV at a stopping location (e.g., in a pickuparea where a user is informed of the location of the AGV and meets theAGV for acquiring an ordered item), the stopping location may need to beat a location where the AGV can safely wait for the user (e.g., to theside of a sidewalk, or otherwise in a space that is not in the way ofother activities or pathways of travel for other entities, and where theuser can easily find the AGV, etc.).

In various implementations, the criteria may also be related to certaintiming considerations. For example, if a transportation vehicle and/orAGVs will be required to stop for a specified period (e.g., 15 minutes,4 hours, etc.), the criteria may require that the stopping location beavailable for that time period. In some instances, the amount of timethat a transportation vehicle will be required to stop for may depend onwhether the transportation vehicle will be waiting at the location forcertain AGVs and/or other autonomous vehicle to arrive/return (e.g.,which may require longer periods of time than deploying AGVs and/orproviding items to AGVs that are already waiting for the transportationvehicle). In some implementations, some stopping locations that arelocated throughout a region may be reserved for use by thetransportation vehicles, AGVs, and/or other commercial vehicles (e.g.,during certain times of day and/or for certain amounts of time, such as30 minutes, 2 hours, etc.) In various implementations, certain stoppinglocations may generally be more available during certain time periods.For example, if certain activities (e.g., deployment, meeting, etc.) ofthe transportation vehicle and/or AGVs are conducted during certain timeperiods (e.g., between 2:00 a.m. and 6:00 a.m., etc.), certain stoppinglocations (e.g., parking locations, sidewalk locations, etc.) maygenerally be more available (e.g., less utilized, less crowded, etc.)and may have fewer timing restrictions.

In some instances, a transportation vehicle and/or AGVs may park orotherwise stop in a first stopping location during a first portion of atime period, and then may move to a second stopping location during asecond portion of a time period (e.g., due to no stopping locationscurrently being available for the full time period). In variousimplementations, certain sensors of the transportation vehicle and/orAGVs may be utilized to read parking signs or otherwise obtaininformation regarding a stopping location (e.g., for determining maximumparking time limits, the available area of the stopping location, etc.).In some instances, stopping locations for a group of AGVs may not allneed to be adjacent to a stopping location for the transportationvehicle, in that the AGVs may wait at stopping locations in a meetingarea that are near to where the stopping location for the transportationvehicle will be, and then may move (e.g., in small groups and/orindividually, etc.) to be adjacent to the transportation vehicle forreceiving items after the transportation vehicle arrives. If no foundstopping location(s) are determined to meet the required criteria, theprocess returns to 1202, where the search continues for other availablestopping location(s).

If the found stopping location(s) do meet the criteria, a determinationis made as to whether to park in a stopping location, as in 1206. Incertain implementations, if the transportation vehicle itself has beensearching for and has found a stopping location that meets the criteria,the transportation vehicle may immediately park in the stopping locationfor the transportation vehicle. However, as noted above, in someinstances it may be AGVs that have been searching for the stoppinglocation(s), in which case the determination may be as to whether one ormore of the AGVs should stop/park in the stopping location for thetransportation vehicle. For example, one or more of the AGVs maystop/park in the stopping location for the transportation vehicle tohold the stopping location for the transportation vehicle until thetransportation vehicle arrives, and/or one or more of the AGVs mayremain in the stopping locations for the AGVs which may be adjacent ornear the stopping location for the transportation vehicle. In variousimplementations, the determination may be made based at least in part onhow soon the transportation vehicle is expected to arrive and well ascertain policies regarding such timing. For example, if thetransportation vehicle is expected to arrive relatively shortly (e.g.,less than a minute), it may be determined that the AGV or otherautonomous vehicle should park in the stopping location to hold it forthe transportation vehicle. In various implementations, the AGVs mayalso congregate in the stopping location for the transportation vehiclewhile they wait for the transportation vehicle (e.g., so as to not takeup space or otherwise be in the way on a sidewalk etc. while they wait).In such instances, the AGVs may move (e.g., up on a sidewalk, to theback or side of the parking space, etc.) to make room for thetransportation vehicle to park once it arrives. If the vehicle(s) (e.g.,AGVs, transportation vehicle, etc.) are to park in the stoppinglocation, the vehicle(s) maneuver to park in the stopping location, asin 1208.

Once the vehicle(s) have stopped/parked in the stopping location(s), asin 1208, or if the vehicle(s) are not to park in the stoppinglocation(s) but the stopping location(s) are still determined to beavailable, as in 1206, notifications regarding the stopping location(s)may be sent, as in 1210. In various implementations, in instances wherethe transportation vehicle itself has found and parked in the stoppinglocation, such notifications may be sent from the transportation vehicleto a remote computing resource (e.g., a management system), or directlyto AGVs and/or other autonomous vehicles that are travelling to meet thetransportation vehicle, etc. Such notifications may include informationregarding not only the transportation vehicle stopping location, butalso regarding located/visible stopping locations for the AGVs that areadjacent to or near the stopping location for the transportation vehicle(e.g., informing the AGVs where they should line up and on which side ofthe transportation vehicle, etc.). In some instances, a managementsystem may determine when a transportation vehicle is parked within adelivery area (e.g., according to a notification that is received fromthe transportation vehicle or as otherwise determined from GPS or othersensor data, etc.) and may send a notification and/or instructions toAGVs that indicates the stopping location where the transportationvehicle is parked and the available stopping locations for the AGVs. Invarious implementations, in instances where an AGV or other autonomousvehicle has found the stopping location(s), notifications regarding thestopping location(s) may be sent from the AGV or other autonomousvehicle (e.g., to the transportation vehicle, to other AGVs travellingto meet the transportation vehicle, to a management system, etc.)indicating the coordinates and/or other information/data regarding thestopping location (e.g., where the transportation vehicle is expected topark once it arrives). In an instance where a transportation vehicleand/or AGV is to park in a first stopping location during a firstportion of a time period, and then move to a second stopping locationduring a second portion of a time period (e.g., due to no stoppinglocations currently being available for the full time period),corresponding notifications (e.g., indicating when the transportationvehicle and/or AGV is to move, etc.) may be sent to the managementsystem, AGVs, transportation vehicle, etc.

After the notifications are sent, a determination may be made as towhether relocation may be required, as in 1212. In variousimplementations, such determinations may be made at regular timeintervals or in response to certain events (e.g., some of the stoppinglocations in a meeting area being taken, etc.). In variousimplementations, relocation of stopping location(s) may be implementedfor various reasons. As an example, a determination may be made that agroup of AGVs that have congregated to meet a transportation vehicle maybe able to move to a closer and/or more convenient meeting area formeeting with the transportation vehicle, in which case relocation may beimplemented. As another example, a planned meeting area may not havesufficient space and/or stopping locations for either the AGVs and/orthe transportation vehicle as the vehicles arrive (e.g., a previouslyavailable parking space may have been taken, a sidewalk may have becomecrowded, etc.), in which case relocation may be required. As anotherexample, a parking time limit may have expired in a first stoppinglocation, requiring relocation to a second stopping location. If thevehicles are to relocate, the process returns to 1202, where newstopping location(s) are searched for, otherwise the process completes,as in 1214.

FIG. 13 is a flow diagram illustrating an example process 1300 for apositioning of an AGV relative to other AGVs in a meeting area,according to some implementations. The example process begins with adetermination of an arrangement of the AGVs in the meeting area, as in1302. In various implementations, after an AGV arrives in a meetingarea, a determination may be made as to whether other AGVs are alreadypresent in the meeting area (e.g., utilizing various sensors of the AGVsthat may provide sensed data indicating the presence of one or moreother AGVs and/or as indicated by a management system, etc.). In variousimplementations, the determination of the arrangement of the AGVs in themeeting area may be made by a management system, or a control system ofa transportation vehicle, or by a control system of one or more of theAGVs, and may be communicated to each of the AGVs through wirelesscommunications (e.g., through a network interface, etc.). In variousimplementations, coordination may be performed between the managementsystem, transportation vehicle and/or AGVs to determine the arrangementof the AGVs in the meeting area.

In various implementations, if the meeting area is for meeting atransportation vehicle, the AGVs may be arranged to each be positionedin a particular stopping location in a particular order. For example,the AGVs may be lined up in an order according to the delivery addresseswhere the AGVs will be delivering items. As another example, the AGVsmay be arranged in an order according to an arranged order of items thatare stored in a transportation vehicle. In various implementations, inaddition to being lined up, the AGVs may also be arranged in otherpatterns and/or configurations (e.g., arranged in geometric patterns orconfigurations, stacked, etc.). It will be appreciated that sucharrangements of AGVs at the meeting area may simplify the transfer ofitems from the transportation vehicle to the AGVs. In variousimplementations, the AGVs may also include markings or other identifyingsymbols or devices (e.g., flashing lights, sounds, etc.) for simplifyingthe identification and transfer of corresponding items from thetransportation vehicle. In various implementations, if the meeting areais a pickup area where items will be retrieved by users, the AGVs may bearranged to be positioned in particular stopping locations according tovarious factors at the pickup area. For example, an AGV that is expectedto be departing shortly may be arranged to be at the outside of aconfiguration (e.g., so as to cause less disruption to the arrangementof the other AGVs when the AGV departs).

In various implementations, the determination of the arrangement of theAGVs may involve coordination between the AGVs, transportation vehicle,and/or management system, etc. For example, one or more of the AGVs maytransmit current positions, information regarding items beingtransported, planned travel paths, delivery timing requirements,available space in the meeting area, and/or other relevant informationto be utilized for determining the arrangement. As part of thecoordination process, one or more of the AGVs may also transmit asuggested arrangement and/or suggested stopping location(s) (e.g., oneAGV may send a communication including a suggested arrangement and/orsuggested stopping location(s), and the other AGV(s), transportationvehicle and/or management system may respond with a communicationincluding either a confirmation or else a suggested alternativearrangement or suggested alterative stopping location(s), etc.)

Once the arrangement of the AGVs has been determined, the AGV ispositioned relative to the other AGVs in the meeting area according tothe determined arrangement, as in 1304. For example, the AGV may beinstructed to move to a designated stopping location at a designedposition within the arrangement, and other AGVs that are already in themeeting area may be instructed to move to accommodate the positioning ofthe AGV. Once the AGV has been positioned relative to the other AGVs,various notifications may be sent regarding the positioning of the AGVin the meeting area, as in 1306. For example, a management system may besent a notification (e.g., which may be utilized to update a databasewith the information regarding the positioning of the AGV in the meetingarea, etc.). As another example, a user may be sent a notificationindicating that the AGV is positioned in the meeting area (e.g., as aconfirmation to the user that an AGV that is to be delivering an item iswaiting for a transportation vehicle to provide the item, or that an AGVin a pickup area has arrived and is available for a user to retrieve anitem, etc.).

After any notifications have been sent, a determination is made if arepositioning of the AGV is required, as in 1308. In variousimplementations, such determinations may be made in response to certainevents or at certain time intervals. For example, if an AGV has arrivedat, or is departing from, a meeting area, a determination may be made asto whether any of the remaining AGVs in the meeting area should berepositioned (e.g., to fill a gap left by the departing AGV). As anotherexample, if information is received indicating that an order and/orarrangement of items in a transportation vehicle has changed, an AGV maybe repositioned according to the new order (e.g., as described abovewith respect to FIG. 7C). If it is determined that repositioning isrequired, the process returns to block 1302 where the new arrangement ofAGVs in the meeting area is determined, otherwise the process completesas in 1310.

FIG. 14 is a flow diagram illustrating an example process 1400 for aremoval of an item from a storage compartment of an AGV, according tosome implementations. The example process begins with the receipt of aninput (e.g., an access code and/or instructions) at a control system ofthe AGV, as in 1402. For example, a user may enter an access code on auser interface of the AGV. In various implementations, an access codemay include a unique identifier, such as a PIN that may be input by theuser. The access code may have been provided to the user as part of amessage indicating that the item was to be delivered by the AGV. In analternative implementation, rather than the user providing an accesscode on the user interface, the control system may receive an input ofan access code or other instructions from a remote computing resource.For example, a user may be instructed to perform an activity such asresponding to a text message or performing another action with theircell phone or other device (e.g., after the AGV has arrived at adelivery location, after the user has met the AGV in a pickup area,etc.) in order to have an access code or other instructions sent from aremote computing resource to the control system of the AGV for providingaccess to the storage compartment. As another example, an access code orother instructions may be automatically sent to the AGV control systemupon arrival at a designated location (e.g., a delivery location mayinclude a system or device that automatically transmits a code orinstructions once the AGV has arrived at the delivery location, asdetermined by one or more sensors, GPS tracking, etc.).

Once the access code or other instructions are received, the storagecompartment associated with the access code or other instructions isunlocked so as to enable the item to be removed from the storagecompartment, as in 1404. For example, a user may reach into the storagecompartment to retrieve the item. As another example, an item engagementmechanism (e.g., a robotic arm, etc.) of the AGV, delivery location,etc., may be utilized to remove the item from the storage compartment.Once the item has been removed, a confirmation is made that the item hasbeen removed from the storage compartment, as in 1406. For example, theconfirmation may include determining whether a closed-door notificationhas been received, as indicating that the door of the storagecompartment has been closed after the item has been removed. Inaddition, if an image capture device 273 within the storage compartmenthas been activated, video or images captured by the image capture device273 may be reviewed or analyzed to confirm that the item has beenremoved from the storage compartment. In addition, or as an alternativethereto, a presence detection sensor 271 and/or motion sensor 272 withinthe storage compartment may be queried to confirm that the item has beenremoved from the storage compartment.

Once a confirmation has been made that the item has been removed fromthe storage compartment, the control system of the AGV sends anotification confirming the removal of the item to a remote computingresource and/or to a user, etc., as in 1408. The confirmation of theremoval of the item may also include additional information such as thedate and time of the removal. In various implementations, a message maybe sent to the user confirming the removal, as a safety measure toensure that it was the user or a user's authorized agent and not anotherparty that removed the item from the storage compartment. In variousimplementations, the notification confirming the removal of the item mayalso correspond to and/or otherwise serve as a notification confirmingthat the item has been delivered to the location where the item wasremoved from the storage compartment.

FIG. 15 is a flow diagram illustrating an example process 1500 for anAGV delivering a storage compartment portion to a location, according tosome implementations. The example process begins with a receipt of anaccess code and/or instructions to release the storage compartmentportion, as in 1502. For example, a control system of an AGV may receivean access code and/or instructions from a remote computing resource(e.g., a management system 326), or as transmitted locally from adelivery location once an AGV arrives, or as provided from a user'selectronic device, or as manually input by a user on a user interface ofthe AGV, etc. Once the access code and/or instructions have beenreceived, the storage compartment portion is released at the deliverylocation, as in 1504. For example, as described above with respect toFIGS. 2A-2C and 8, the storage compartment portion may be unlockedand/or otherwise released from a propulsion portion, so that the storagecompartment portion may be left at the delivery location while thepropulsion portion departs from the delivery location. In variousimplementations, a storage compartment detachment and/or movementmechanism (e.g., rollers 234) may be utilized to assist with the removaland delivery of the storage compartment portion to the deliverylocation.

Once the storage compartment portion has been released and delivered atthe delivery location, one or more notifications may be sent confirmingthe delivery of the storage compartment portion to the deliverylocation, as in 1506. For example, a notification may be sent to a userconfirming that the storage compartment portion has been delivered tothe delivery location (e.g., at a user's residence, etc.). As anotherexample, a notification may be sent to a management system that may beutilized to update a database with the delivery information. As anotherexample, a notification may be sent to a second AGV that is to furthertransport the storage compartment portion. In various implementations,after the storage compartment portion is delivered, the propulsionportion of the AGV may continue travel to another designated location(e.g., to a home base location, to a transportation vehicle, etc.). Invarious implementations, the storage compartment portion may be furthertransported from the location to another location by a second AGV. Forexample, a management system may direct a propulsion portion of a secondAGV to travel to the location so that the storage compartment portionmay be coupled to the propulsion portion of the second AGV. The secondAGV may further be instructed to travel from the location to a secondlocation where the storage compartment portion is to be delivered.

FIG. 16 is a block diagram illustrating an example AGV control system210, such as may be utilized for the AGVs 200 of FIGS. 2A-8, or forother types of AGVs. In various examples, the block diagram of FIG. 16may be illustrative of one or more aspects of the AGV control system 210that may be used to implement the various systems and methods discussedherein. In the illustrated implementation, the AGV control system 210includes one or more processors 1602 coupled to a non-transitorycomputer readable storage medium 1620 via an input/output (I/O)interface 1610. The AGV control system 210 may also include a propulsioncontroller 1604 (e.g., for controlling one or more motors, engines,etc.), a power controller 1606 (e.g., for controlling, monitoring and/orregulating the use and charging of the power modules) and/or anavigation system 1608. The AGV control system 210 further includes anitem engagement mechanism controller 1612, a network interface 1616, andone or more input/output devices 1618.

In various implementations, the AGV control system 210 may be auniprocessor system including one processor 1602, or a multiprocessorsystem including several processors 1602 (e.g., two, four, eight, oranother suitable number). The processor(s) 1602 may be any suitableprocessor capable of executing instructions. For example, in variousimplementations, the processor(s) 1602 may be general-purpose orembedded processors implementing any of a variety of instruction setarchitectures (ISAs), such as the x86, PowerPC, SPARC, or MIPS ISAs, orany other suitable ISA. In multiprocessor systems, each processor(s)1602 may commonly, but not necessarily, implement the same ISA.

The non-transitory computer readable storage medium 1620 may beconfigured to store executable instructions, data, travel paths, and/ordata items accessible by the processor(s) 1602. In variousimplementations, the non-transitory computer readable storage medium1620 may be implemented using any suitable memory technology, such asstatic random access memory (SRAM), synchronous dynamic RAM (SDRAM),nonvolatile/Flash-type memory, or any other type of memory. In theillustrated implementation, program instructions and data implementingdesired functions, such as those described herein, are shown storedwithin the non-transitory computer readable storage medium 1620 asprogram instructions 1622, data storage 1624 and travel path data 1626,respectively. In other implementations, program instructions, data,and/or travel paths may be received, sent, or stored upon differenttypes of computer-accessible media, such as non-transitory media, or onsimilar media separate from the non-transitory computer readable storagemedium 1620 or the AGV control system 210. Generally speaking, anon-transitory, computer readable storage medium may include storagemedia or memory media such as magnetic or optical media, e.g., disk orCD/DVD-ROM, coupled to the AGV control system 210 via the I/O interface1610. Program instructions and data stored via a non-transitory computerreadable medium may be transmitted by transmission media or signals suchas electrical, electromagnetic, or digital signals, which may beconveyed via a communication medium such as a network and/or a wirelesslink, such as may be implemented via the network interface 1616.

In one implementation, the I/O interface 1610 may be configured tocoordinate I/O traffic between the processor(s) 1602, the non-transitorycomputer readable storage medium 1620, and any peripheral devices, thenetwork interface or other peripheral interfaces, such as input/outputdevices 1618. In some implementations, the I/O interface 1610 mayperform any necessary protocol, timing or other data transformations toconvert data signals from one component (e.g., non-transitory computerreadable storage medium 1620) into a format suitable for use by anothercomponent (e.g., processor(s) 1602). In some implementations, the I/Ointerface 1610 may include support for devices attached through varioustypes of peripheral buses, such as a variant of the Peripheral ComponentInterconnect (PCI) bus standard or the Universal Serial Bus (USB)standard, for example. In some implementations, the function of the I/Ointerface 1610 may be split into two or more separate components, suchas a north bridge and a south bridge, for example. Additionally, in someimplementations, some or all of the functionality of the I/O interface1610, such as an interface to the non-transitory computer readablestorage medium 1620, may be incorporated directly into the processor(s)1602.

The propulsion controller 1604 communicates with the navigation system1608 (e.g., for adjusting the steering and power of the motor of the AGV200 to guide the AGV along a determined travel path). The navigationsystem 1608 may include a global positioning system (GPS), indoorpositioning system (IPS), or other similar system and/or sensors thatcan be used to navigate the AGV 200 to and/or from a location. The itemengagement mechanism controller 1612 is utilized to engage and/ordisengage items that are to be acquired and/or delivered by the AGV 200.For example, the item engagement mechanism controller 1612 may operatean item engagement mechanism that includes a robotic arm or othermechanism for engaging items and placing them in a storage compartmentof the AGV 200, or for removing items from a storage compartment andplacing them at a delivery location or other location. In variousconfigurations, the item engagement mechanism may be powered by thepower modules, motors, etc. of the AGV 200.

The network interface 1616 may be configured to allow data to beexchanged between the AGV control system 210, other devices attached toa network and/or the AGV, such as other computer systems (e.g., remotecomputing resources 310), and/or with AGV control systems of other AGVs.For example, the network interface 1616 may enable wirelesscommunication between the AGV 200 and the management system 326 that isimplemented on one or more of the remote computing resources 310. Forwireless communication, an antenna of an AGV or other communicationcomponents may be utilized. As another example, the network interface1616 may enable wireless communication between numerous AGVs. In variousimplementations, the network interface 1616 may support communicationvia wireless general data networks, such as a Wi-Fi network. Forexample, the network interface 1616 may support communication viatelecommunications networks such as cellular communication networks,satellite networks, and the like. Communications through wiredconnections (e.g., through coupling portions 205) may also be supported(e.g., for communicating with other coupled AGVs, control stations,docking stations, other control systems and/or networks, etc.).

In some implementations, with respect to the operations of the userinterface 211 and/or operations for accessing the storagecompartment(s), receiving items, etc., the input/output devices 1618 mayinclude one or more display terminals, keyboards, keypads, touchpads,scanning devices, voice or optical recognition devices, sensors, or anyother devices suitable for entering or retrieving data or sensinginputs. Multiple input/output devices 1618, some of which may beincluded as part of the user interface 211, may be present in orotherwise controlled by the AGV control system 210 or may be distributedon various nodes of the AGV control system 210. In some implementations,similar input/output devices may be separate from the AGV control system210 and may interact with one or more nodes of the AGV control system210 through a wired or wireless connection, such as over the networkinterface 1616. In various implementations, a storage compartmentportion 202 and/or various components thereof (e.g., sensors, userinterface, etc.) may function as input/output device(s) with respect tothe AGV control system 210 (e.g., as coupled through various couplingportions as described above with respect to FIGS. 2A-2C). Similarly, insome implementations, movement mechanisms 234 (e.g., for assisting withthe movement of a storage compartment portion 202 forcoupling/decoupling from a propulsion portion 201) may be operated asinput/output devices by the AGV control system 210.

In some implementations, with respect to the navigation, etc. of the AGV200, the input/output devices 1618 may include one or more displays,imaging sensors, thermal sensors, infrared sensors, time of travelsensors, accelerometers, weather sensors, locator devices, etc. Multiplesuch input/output devices 1618 may be present and controlled by the AGVcontrol system 210. One or more of these sensors (e.g., imaging sensors,etc.) may be utilized to assist with navigating the AGV 200 along travelpaths (e.g., including the avoidance of other vehicles or obstaclesduring travel, etc.). In various implementations, such sensors may alsobe utilized for assisting with the positioning of the AGV 200 relativeto other AGVs in a meeting area and/or other activities of the AGV 200.For example, an imaging sensor may be utilized to assist withnavigation, as well determining an identification of a transportationvehicle from which an item is to be received and/or an identification ofan item that is to be received.

As shown in FIG. 16, the memory may include program instructions 1622that may be configured to implement the example processes and/orsub-processes described herein. The data storage 1624 may includevarious data stores for maintaining data items that may be provided fordetermining travel paths, receiving and delivering items, identifyinglocations, etc. In various implementations, the parameter values andother data illustrated herein as being included in one or more datastores may be combined with other information not described or may bepartitioned differently into more, fewer, or different data structures.In some implementations, data stores may be physically located in onememory or may be distributed among two or more memories.

Those skilled in the art will appreciate that the AGV control system 210is merely illustrative and is not intended to limit the scope of thepresent disclosure. In particular, the computing system and devices mayinclude any combination of hardware or software that can perform theindicated functions, including computers, network devices, internetappliances, PDAs, wireless phones, pagers, etc. The AGV control system210 may also be connected to other devices that are not illustrated, orinstead may operate as a stand-alone system. In addition, thefunctionality provided by the illustrated components may in someimplementations be combined in fewer components or distributed inadditional components. Similarly, in some implementations, thefunctionality of some of the illustrated components may not be providedand/or other additional functionality may be available.

Those skilled in the art will also appreciate that, while various itemsare illustrated as being stored in memory or storage while being used,these items or portions of them may be transferred between memory andother storage devices for purposes of memory management and dataintegrity. Alternatively, in other implementations, some or all of thesoftware components may execute in memory on another device andcommunicate with the illustrated AGV control system 210. Some or all ofthe system components or data structures may also be stored (e.g., asinstructions or structured data) on a non-transitory,computer-accessible medium or a portable article to be read by anappropriate drive, various examples of which are described herein. Insome implementations, instructions stored on a computer-accessiblemedium separate from the AGV control system 210 may be transmitted tothe AGV control system 210 via transmission media or signals such aselectrical, electromagnetic, or digital signals, conveyed via acommunication medium such as a wireless link. Various implementationsmay further include receiving, sending, or storing instructions and/ordata implemented in accordance with the foregoing description upon acomputer-accessible medium. Accordingly, the techniques described hereinmay be practiced with other AGV control system configurations.

While the functional components of the example AGV 200 are discussedherein as part of the AGV 200, in other implementations, one or more ofthe functional components may be distributed and/or implemented as partof the management system 326. For example, one or more of the aspects ofthe program instructions 1622 may be implemented as part of themanagement system 326.

FIG. 17 is a block diagram of an illustrative implementation of a serversystem, such as the server system 320, which may be used in theimplementations described herein. The server system 320 may include aprocessor 1700, such as one or more redundant processors, a videodisplay adapter 1702, a disk drive 1704, an input/output interface 1706,a network interface 1708, and a memory 1712. The processor 1700, thevideo display adapter 1702, the disk drive 1704, the input/outputinterface 1706, the network interface 1708, and the memory 1712 may becommunicatively coupled to each other by a communication bus 1710.

The video display adapter 1702 provides display signals to a localdisplay (not shown in FIG. 17) permitting an agent of the server system320 to monitor and configure operation of the server system 320 and/orto provide information (e.g., regarding the operations of AGVs 200,transportation vehicles 332, etc.). The input/output interface 1706likewise communicates with external input/output devices not shown inFIG. 17, such as a mouse, keyboard, scanner, or other input and outputdevices that can be operated by an agent of the server system 320. Thenetwork interface 1708 includes hardware, software, or any combinationthereof, to communicate with other computing devices. For example, thenetwork interface 1708 may be configured to provide communicationsbetween the server system 320 and other computing devices, such as thatof an AGV 200, transportation vehicle 332, management system 326, etc.,via a network.

The memory 1712 generally comprises random access memory (RAM),read-only memory (ROM), flash memory, and/or other volatile or permanentmemory. The memory 1712 is shown storing an operating system 1714 forcontrolling the operation of the server system 320. A binaryinput/output system (BIOS) 1716 for controlling the low-level operationof the server system 320 is also stored in the memory 1712.

The memory 1712 additionally stores program code and data for providingnetwork services to the AGVs 200, the transportation vehicles 332, themanagement system 326, etc. Accordingly, the memory 1712 may store abrowser application 1718. The browser application 1718 comprisescomputer executable instructions, that, when executed by the processor1700 generate or otherwise obtain configurable markup documents such asWeb pages. The browser application 1718 communicates with a data storemanager application 1720 to facilitate data exchange between the datastore 1730 and the AGVs 200, the transportation vehicles 332, themanagement system 326, etc.

As used herein, the term “data store” refers to any device orcombination of devices capable of storing, accessing, and retrievingdata, which may include any combination and number of data servers,databases, data storage devices and data storage media, in any standard,distributed or clustered environment. The server system 320 can includeany appropriate hardware and software for integrating with the datastore 1730 as needed to execute aspects of one or more applications foran AGV 200, a transportation vehicle, a management system 326, etc.

The data store 1730 can include several separate data tables, databasesor other data storage mechanisms and media for storing data relating toa particular aspect. For example, the illustrated data store 1730 mayinclude mechanisms for maintaining information related to operations,inventory, maps, GPS data, AGVs, delivery locations, home baselocations, meeting areas, associated travel paths, etc., which can beused to generate and deliver information to an AGV 200, a transportationvehicle 332, a management system 326, agents, etc. It should beunderstood that there may be additional aspects that can be stored inthe data store 1730 and that additional data stores beyond the oneillustrated may be included. The data store 1730 is operable, throughlogic associated therewith, to receive instructions from the serversystem 320 and obtain, update or otherwise process data in responsethereto.

The memory 1712 may also include the management system 326, discussedabove. The management system 326 may be executable by the processor 1700to implement one or more of the functions of the server system 320. Inone implementation, the management system 326 may represent instructionsembodied in one or more software programs stored in the memory 1712. Inanother implementation, the management system 326 can representhardware, software instructions, or a combination thereof.

The server system 320, in one implementation, is a distributedenvironment utilizing several computer systems and components that areinterconnected via communication links, using one or more computernetworks or direct connections. However, it will be appreciated by thoseof ordinary skill in the art that such a system could operate equallywell in a system having fewer or a greater number of components than areillustrated in FIG. 17. Thus, the depiction in FIG. 17 should be takenas being illustrative in nature and not limiting to the scope of thedisclosure.

Those skilled in the art will appreciate that in some implementationsthe functionality provided by the processes and systems discussed abovemay be provided in alternative ways, such as being split among moresoftware modules or routines or consolidated into fewer modules orroutines. Similarly, in some implementations, illustrated processes andsystems may provide more or less functionality than is described, suchas when other illustrated processes instead lack or include suchfunctionality respectively, or when the amount of functionality that isprovided is altered. In addition, while various operations may beillustrated as being performed in a particular manner (e.g., in serialor in parallel) and/or in a particular order, those skilled in the artwill appreciate that in other implementations the operations may beperformed in other orders and in other manners. Those skilled in the artwill also appreciate that the data structures discussed above may bestructured in different manners, such as by having a single datastructure split into multiple data structures or by having multiple datastructures consolidated into a single data structure. Similarly, in someimplementations, illustrated data structures may store more or lessinformation than is described, such as when other illustrated datastructures instead lack or include such information respectively, orwhen the amount or types of information that is stored is altered. Thevarious methods and systems as illustrated in the figures and describedherein represent example implementations. The methods and systems may beimplemented in software, hardware, or a combination thereof in otherimplementations. Similarly, the order of any method may be changed andvarious elements may be added, reordered, combined, omitted, modified,etc., in other implementations.

From the foregoing, it will be appreciated that, although specificimplementations have been described herein for purposes of illustration,various modifications may be made without deviating from the spirit andscope of the appended claims and the elements recited therein. Inaddition, while certain aspects are presented below in certain claimforms, the inventors contemplate the various aspects in any availableclaim form. For example, while only some aspects may currently berecited as being embodied in a computer readable storage medium, otheraspects may likewise be so embodied. Various modifications and changesmay be made as would be obvious to a person skilled in the art havingthe benefit of this disclosure. It is intended to embrace all suchmodifications and changes and, accordingly, the above description is tobe regarded in an illustrative rather than a restrictive sense.

What is claimed is:
 1. A system to transport an ordered item, the systemcomprising: a materials handling facility containing an ordered item tobe delivered by an autonomous ground vehicle (AGV) to a deliverylocation in a delivery area; an AGV facility that is mobile and isconfigured to be temporarily located at a stopping location in thedelivery area; a transportation vehicle configured to transport theordered item from the materials handling facility to the AGV facility atthe stopping location in the delivery area; an AGV to be deployed fromthe AGV facility to deliver the ordered item from the AGV facility tothe delivery location, the AGV comprising: a propulsion portion; a powermodule for supplying power to the propulsion portion; a storagecompartment having a locking mechanism; and a control system,comprising: one or more processors; and a memory coupled to the one ormore processors and storing program instructions that when executed bythe one or more processors cause the one or more processors to at least:control the propulsion portion to deploy the AGV from the AGV facilitythat is at the stopping location in the delivery area with the ordereditem contained in the storage compartment of the AGV; control thepropulsion portion to navigate the AGV along a travel path from the AGVfacility to the delivery location; and control the locking mechanismafter the AGV has arrived at the delivery location to unlock the storagecompartment to enable the ordered item to be removed from the storagecompartment.
 2. The system of claim 1, wherein the AGV facility that ismobile is of a size that fits within a 9 foot by 18 foot parking space.3. The system of claim 2, wherein the AGV facility comprises an itemengagement mechanism that is configured to place the item in the storagecompartment of the AGV.
 4. The system of claim 3, wherein the itemengagement mechanism comprises a mechanical arm.
 5. A transportationsystem, comprising: a first autonomous ground vehicle (AGV) comprising:a first storage compartment having a first locking mechanism; a firstcontrol system configured to control the first locking mechanism; and afirst propulsion portion; an AGV facility that the first AGV isconfigured to deploy from and that is mobile and is configured to betemporarily located at a stopping location in a delivery area; and acomputing system, comprising: one or more processors; and a memorycoupled to the one or more processors and storing program instructionsthat when executed by the one or more processors cause the one or moreprocessors to at least: provide instructions for an item to be to betransported by a transportation vehicle from a materials handlingfacility to the AGV facility at the stopping location in the deliveryarea; provide instructions for the first AGV to deploy from the AGVfacility with the item in the first storage compartment; provideinstructions for the first AGV to follow a travel path to deliver theitem to a first delivery location that is in the delivery area; andprovide instructions for the first AGV to follow the travel path toreturn to the AGV facility after completing the delivery of the item tothe first delivery location.
 6. The system of claim 5, wherein the AGVfacility comprises a door that requires an access code to open, and thefirst AGV further comprises an access mechanism that wirelesslytransmits the access code to open the door to enable the first AGV to atleast one of enter or exit the AGV facility.
 7. The system of claim 5,wherein the AGV facility comprises an item engagement mechanism that isconfigured to place the item in the first storage compartment of thefirst AGV.
 8. The system of claim 7, wherein the item engagementmechanism comprises a mechanical arm.
 9. The system of claim 5, whereonthe travel path is a first travel path, the system further comprising: asecond AGV comprising: a second storage compartment having a secondlocking mechanism; a second control system configured to control thesecond locking mechanism; and a second propulsion portion; and whereinthe program instructions when executed by the one or more processorsfurther cause the one or more processors to: instruct the second AGV todeploy from the AGV facility; instruct the second AGV to follow a secondtravel path to deliver an item to a second delivery location; andinstruct the second AGV to follow the second travel path to return tothe AGV facility after completing the delivery of the item to the seconddelivery location.
 10. The system of claim 9, wherein the AGV facilityis large enough to contain the first and second AGVs at the same time.11. The system of claim 10, wherein the AGV facility is of a size thatfits within a 9 foot by 18 foot parking space.
 12. The system of claim10, wherein the AGV facility is configured to store the first and secondAGVs when the first and second AGVs are not performing deliveries orother activities.
 13. A computer implemented method to transport anitem, the computer implemented method comprising: under control of oneor more computing systems configured with executable instructions,providing instructions for an AGV facility that is mobile to betemporarily located at a stopping location in a delivery area; receivingan order for a first item that is to be delivered by a first autonomousground vehicle (AGV) to a first delivery location that is in thedelivery area; providing instructions for the first item to betransported by a transportation vehicle from a materials handlingfacility to the AGV facility; providing instructions for the first AGVto receive the first item in a storage compartment of the first AGV atthe AGV facility; and providing instructions for the first AGV to followa travel path from the AGV facility to the first delivery location todeliver the first item.
 14. The computer implemented method of claim 13,wherein the travel path is a first travel path, the method furthercomprising: receiving an order for a second item that is to be deliveredby a second AGV to a second delivery location; providing instructionsfor the second item to be transported by the transportation vehicle fromthe materials handling facility to the AGV facility at the same timethat the first item is transported by the transportation vehicle to theAGV facility; providing instructions for the second AGV to receive thesecond item in a storage compartment of the second AGV at the AGVfacility; and providing instructions for the second AGV to follow asecond travel path from the AGV facility to the second delivery locationto deliver the second item.
 15. The computer implemented method of claim14, wherein the AGV facility is a home base location for the first andsecond AGVs, and the method further comprises providing instructions forthe first and second AGVs to follow respective travel paths to return tothe AGV facility after completing the deliveries to the respective firstand second delivery locations.
 16. The computer implemented method ofclaim 14, further comprising providing instructions for the first andsecond items to be removed from the transportation vehicle and placed inthe respective first and second storage compartments while the first andsecond AGVs are inside the AGV facility.
 17. The computer implementedmethod of claim 13, further comprising providing instructions for thefirst AGV and a second AGV to utilize respective coupling portions tocouple to respective docking stations inside the AGV facility.
 18. Thecomputer-implemented method of claim 13, wherein the AGV facility thatis mobile is of a size that fits within a 9 foot by 18 foot parkingspace, and the instructions for the AGV facility to be positioned at thestopping location include instructions for searching for an availableparking space in the delivery area where the AGV facility may be parked.19. The computer-implemented method of claim 18, wherein the AGVfacility comprises an item engagement mechanism and thecomputer-implemented method further comprises providing instructions forthe item engagement mechanism to place the item in the storagecompartment of the AGV.
 20. The computer-implemented method of claim 19,wherein the item engagement mechanism comprises a mechanical arm and theinstructions for the item engagement mechanism comprise instructions forthe mechanical arm to place the item in the storage compartment of theAGV.